Mercury Spec Ops MCP Server
Related Servers
Alternatives to Mercury Spec Ops MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceTurns AI assistants into full-stack software engineers with 36 tools for cognitive reasoning, code validation, project scaffolding, and AI/IDE configuration generation across 130+ programming languages, databases, and frameworks.359-
- AlicenseAqualityAmaintenanceA comprehensive development toolkit with 23 tools covering code quality analysis, development efficiency, and project management. Enables AI-assisted code review, test generation, performance analysis, SQL generation, UI component creation, and automated project documentation.249636MIT
- FlicenseAqualityBmaintenanceEnables AI assistants to deeply understand codebases via Knowledge Graphs, supporting fuzzy search, architecture layer queries, call chain tracing, impact analysis, and domain knowledge with multi-project support.182-
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with 28 developer tools across file, git, code analysis, HTTP, and system domains, enabling tasks like file editing, repository management, code analysis, and shell command execution.42MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to leverage the BMAD methodology with 11 specialized agents and 36+ workflows for software development tasks.8065ISC
- AlicenseAqualityDmaintenanceEnables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.57MIT
TDQS
Scored across 6 tools
Each tool is clearly tied to a specific domain (PRD, codebase analysis, bug analysis) and a specific action (generate prompt or fetch template). There is no overlap between the six tools, so an agent can reliably select the correct one.
All tool names follow the consistent pattern generate_<domain>_prompt or get_<domain>_template. The distinction between 'prompt' and 'template' is meaningful and matches the tool function, and the domain segment is consistent throughout.
Six tools is well-scoped for a prompt/template serving server. Each tool serves a distinct purpose, and the count is large enough to be useful without being bloated.
For each of the three domains, there is both a prompt generator and a template fetcher, covering the full lifecycle of using these resources. There are no obvious missing operations within the stated purpose of the server.