Plugin Hub
Related Servers
Alternatives to Plugin Hub
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server that enables Claude Code to delegate tasks to DeepSeek and other LLMs, offering 20 tools for code review, analysis, testing, and code generation.201-
- AlicenseCqualityDmaintenanceA comprehensive MCP server that provides AI assistants with tools for file system management, Git integration, and shell command execution. It features specialized code utilities for analysis, formatting, and linting to enhance development workflows within Claude Desktop.287MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides access to over 100 development skills for frontend, backend, integration, design, devops, and process categories via Claude Code and other MCP clients.-
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server with file management, HTTP requests, system info, and environment variable tools, plus a management UI and dual transport for Claude Desktop and Claude.ai.205 npmMIT
- AlicenseAqualityBmaintenanceLocal MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing 35 developer utility APIs (JSON formatting, code review, password generation, etc.) for AI agents like Claude.3-
TDQS
Scored across 616 tools
With 616 tools, there are numerous overlapping and near-duplicate tools across domains. Examples include auth_generate_jwt vs jwt_generate_auth, monitor_setup_grafana vs grafana_generate_dashboard vs prom_generate_dashboards, and queue_setup_bullmq vs jobq_setup_bullmq, making it very difficult for an agent to reliably select the correct tool.
There is a rough pattern of domain_verb_object, but it is inconsistent: many tools invert to verb_domain_object (generate_go_module, scaffold_django_project, setup_python_venv), some use nouns (invoice_generator, usage_tracker), and the same action is variously called generate, setup, add, create, or configure across domains. The mixed conventions hurt predictability.
616 tools is an extreme count for any server. Even if this is a plugin hub aggregating many domains, the sheer number makes selection and navigation impractical, and far exceeds reasonable tool-set scoping.
The tool surface is exceptionally broad, covering dozens of domains with base setup, incremental add-ons, and Pro-tier optimization/reporting tools. There are no obvious dead ends for common generation workflows, though the lack of delete/remove tools might matter in some contexts, but this is not a central expectation for a code-generation plugin hub.