Mercury Spec Ops MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_prd_promptB | Generate an assembled Product Requirements Document prompt with specified technology stacks and analysis focus areas |
| generate_codebase_analysis_promptA | Generate an assembled codebase analysis prompt with specified technology stacks and analysis focus areas |
| generate_bug_analysis_promptC | Generate an assembled bug analysis prompt with specified technology stacks and severity level |
| get_prd_templateA | Fetch a comprehensive Product Requirements Document markdown template with all standard sections (14 sections total) |
| get_codebase_analysis_templateA | Fetch a comprehensive codebase analysis markdown template with all standard sections (12 sections total) |
| get_bug_analysis_templateA | Fetch a comprehensive bug analysis markdown template with all standard sections (8 sections total) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.