Mercury Spec Ops

Mercury Spec Ops MCP Server provides six programmable tools to help AI generate technology-specific prompts and comprehensive templates on-demand. Built for modularity, it enables dynamic prompt assembly across 31 technology stacks, 10 analysis dimensions, and 34 template sections, all accessible through simple tool calls. This makes it easy to create targeted, up-to-date prompts and templates for complex software projects.

How to use

To integrate with an MCP client, configure the Mercury Spec Ops MCP server as a local or remote service that your client can call. You will select prompts and templates programmatically, allowing the AI to generate technology-specific prompts and comprehensive templates on-demand. The server exposes six programmable tools for prompts and resources, and it supports multi-value input so you can analyze multiple technologies and focus areas in a single workflow.

How to install

Prerequisites: Node.js and npm should be installed on your system. You may also use a direct MCP connection via npx if you prefer not to install locally.

# Option 1: Local development
git clone https://github.com/n0zer0d4y/mercury-spec-ops.git
cd mercury-spec-ops
npm install
npm run build

# Start the server locally
npm run mcp

# Option 2: Install from npm
npm install -g @n0zer0d4y/mercury-spec-ops

# Or run directly with npx (no installation required)
npx @n0zer0d4y/mercury-spec-ops

Configuration and usage notes

There are two common MCP integration patterns shown for Mercury Spec Ops. You can use npx for a quick, no-install setup or run a local installation if you prefer hosting the server on your own environment.

# npx usage (recommended for quick start)
{
  "mcpServers": {
    "mercury_specops": {
      "command": "npx",
      "args": ["-y", "@n0zer0d4y/mercury-spec-ops"]
    }
  }
}

Troubleshooting and tips

If you update configuration, restart your MCP client to ensure changes take effect. When using local installation, ensure you have built the project before starting the server. If you encounter timeouts, consider increasing the timeout setting in your MCP client configuration.

Additional usage patterns

The server supports two primary execution modes via MCP tooling: running through npx for rapid experimentation and running via a local Node.js process for production-style deployments. In both modes, you can leverage the six tools to assemble prompts and templates on demand, specifying technology stacks, analysis focuses, and severity levels as needed.

Examples of common workflows

1. Enhanced Codebase Analysis: Prompt the server to analyze a codebase across multiple technologies and focus areas, then assemble a tailored analysis template for review.

2. PRD Generation with Technology Support: Create a PRD for a project by selecting the appropriate technology stack, and let the system assemble a technology-enhanced template for fast, consistent documentation.

Notes on security and maintenance

Keep dependencies up to date and monitor prompts and templates for changes that reflect evolving technology stacks and best practices. Use isolated environments when testing new configurations to avoid interfering with production workflows.

Examples of supported tools and resources

The server exposes six programmable capabilities: three prompts (PRD Prompt, Codebase Analysis Prompt, Bug Analysis Prompt) and three resources (PRD Template, Codebase Analysis Template, Bug Analysis Template). These work together with a modular architecture that supports 31 technology stacks, 10 analysis dimensions, and 34 template sections.

Summary of features

Enum-based input validation, programmable prompt assembly, and a modular template system enable dynamic, technology-aware prompt generation and template construction.

Appendix: Developer notes

Project structure and testing details are available in the source repository. You can run tests with npm test, build for production with npm run build, and lint with npm run lint.

Available tools

prd-prompt

Generates a Product Requirements Document with modular technology-specific analysis.

codebase-analysis-prompt

Analyzes codebases with modular technology-focused analysis.

bug-analysis-prompt

Analyzes bugs with modular severity and technology-specific analysis.

prd-template

Modular PRD template with technology-specific sections.

codebase-analysis-template

Modular codebase analysis template with technology- and focus-specific sections.

bug-analysis-template

Modular bug analysis template with severity- and technology-specific sections.