{"id":43520779,"url":"https://github.com/n0zer0d4y/mercury-spec-ops","last_synced_at":"2026-02-03T14:14:03.737Z","repository":{"id":323971064,"uuid":"1094731007","full_name":"n0zer0d4y/mercury-spec-ops","owner":"n0zer0d4y","description":"Modular MCP server for programmatic prompt engineering. Provides intelligent prompt assembly for PRD generation, codebase analysis, and bug analysis with support for 31 technology stacks.","archived":false,"fork":false,"pushed_at":"2025-12-27T13:33:29.000Z","size":271,"stargazers_count":4,"open_issues_count":0,"forks_count":2,"subscribers_count":0,"default_branch":"master","last_synced_at":"2025-12-29T09:14:06.574Z","etag":null,"topics":["bug-analysis","code-analysis","context-engineering","developer-tools","mcp-server","model-context-protocol","modular-architecture","prompt-assembly","prompt-engineering"],"latest_commit_sha":null,"homepage":"https://www.npmjs.com/package/@n0zer0d4y/mercury-spec-ops","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/n0zer0d4y.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-11-12T05:07:51.000Z","updated_at":"2025-12-27T13:33:34.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/n0zer0d4y/mercury-spec-ops","commit_stats":null,"previous_names":["n0zer0d4y/mercury-spec-ops"],"tags_count":2,"template":false,"template_full_name":null,"purl":"pkg:github/n0zer0d4y/mercury-spec-ops","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n0zer0d4y%2Fmercury-spec-ops","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n0zer0d4y%2Fmercury-spec-ops/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n0zer0d4y%2Fmercury-spec-ops/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n0zer0d4y%2Fmercury-spec-ops/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/n0zer0d4y","download_url":"https://codeload.github.com/n0zer0d4y/mercury-spec-ops/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n0zer0d4y%2Fmercury-spec-ops/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29047548,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-03T10:09:22.136Z","status":"ssl_error","status_checked_at":"2026-02-03T10:09:16.814Z","response_time":96,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bug-analysis","code-analysis","context-engineering","developer-tools","mcp-server","model-context-protocol","modular-architecture","prompt-assembly","prompt-engineering"],"created_at":"2026-02-03T14:14:03.031Z","updated_at":"2026-02-03T14:14:03.724Z","avatar_url":"https://github.com/n0zer0d4y.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Mercury Spec Ops MCP Server: Prompts and Resources as **_Tools_**\n\n![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?logo=typescript\u0026logoColor=white)\n[![MCP Registry](https://img.shields.io/badge/MCP-Registry-blue)](https://registry.modelcontextprotocol.io/servers/io.github.n0zer0d4y/mercury-spec-ops)\n![MCP Dev](https://badge.mcpx.dev?type=dev \"MCP Dev\")\n[![MCP Server](https://badge.mcpx.dev?type=server \"MCP Server\")](https://modelcontextprotocol.io)\n[![MCP Server with Tools](https://badge.mcpx.dev?type=server\u0026features=tools \"MCP server with tools\")](https://modelcontextprotocol.io)\n[![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/n0zer0d4y-mercury-spec-ops-badge.png)](https://mseep.ai/app/n0zer0d4y-mercury-spec-ops)\n\n**The first MCP server to expose dynamic, AI-invocable tools for prompt generation and template assembly.**\n\nTransform how AI assistants interact with specialized content. Instead of static prompts and resources, Mercury Spec Ops provides **6 programmable tools** that enable AI to dynamically generate technology-specific prompts and comprehensive templates on-demand. Built on a sophisticated modular architecture with **31 technology stacks**, **10 analysis dimensions**, and **34 template sections**—all accessible through simple tool calls.\n\n## Features\n\nThis MCP server provides a modular, extensible architecture with:\n\n### Prompts (Enhanced with Enum Support)\n\n1. **PRD Prompt** - Generate Product Requirements Document with modular technology-specific analysis\n2. **Codebase Analysis Prompt** - Analyze codebases with modular technology/focus-specific analysis\n3. **Bug Analysis Prompt** - Analyze bugs with modular severity/technology-specific analysis\n\n### Resources (Modular Templates)\n\n1. **PRD Template** - Modular PRD template with technology-specific sections\n2. **Codebase Analysis Template** - Modular codebase analysis template with technology/focus-specific sections\n3. **Bug Analysis Template** - Modular bug analysis template with severity/technology-specific sections\n\n## Key Capabilities\n\n### Enum-Based Input Validation\n\n- **Technology Stack** (31 total):\n  - **Languages** (11): JavaScript, TypeScript, Python, Java, Go, Rust, C#, PHP, Ruby, Swift, Kotlin\n  - **Runtimes** (1): Node.js\n  - **Frontend** (3): React, Angular, Vue\n  - **Backend** (7): Express, NestJS, Django, Flask, Spring, Laravel, Rails\n  - **Databases** (4): MongoDB, PostgreSQL, MySQL, Redis\n  - **Cloud** (3): AWS, Azure, GCP\n  - **DevOps** (2): Docker, Kubernetes\n- **Analysis Focus** (10 total): architecture, security, performance, testing, documentation, maintainability, scalability, reliability, code-quality, dependencies\n- **Bug Severity** (4 total): low, medium, high, critical\n- **Target Audience**: developers, business-users, enterprise, startup, healthcare, finance, and more\n\n### Programmatic Prompt Assembly\n\n- Base prompts + 31 technology modules + 10 focus modules + 4 severity modules\n- Automatic module selection based on input parameters\n- Priority-based module ordering\n- **Multi-value support**: Analyze multiple technologies and focus areas simultaneously\n- **Comma-separated input**: \"node.js,react,postgresql\" or \"security,performance,code-quality\"\n- Custom instruction integration\n- Intelligent fallback to base prompts\n\n### Modular Template System\n\n- Template sections with dependency resolution\n- Technology-specific template sections\n- Focus-specific template sections\n- Custom section support\n\n## Installation\n\n### Option 1: Local Development\n\n1. Clone and install dependencies:\n\n```bash\ngit clone https://github.com/n0zer0d4y/mercury-spec-ops.git\ncd mercury-spec-ops\nnpm install\nnpm run build\n```\n\n2. Run the server locally:\n\n```bash\nnpm run mcp\n```\n\n### Option 2: Install from npm\n\n```bash\nnpm install -g @n0zer0d4y/mercury-spec-ops\n```\n\nOr use directly with `npx` (no installation required):\n\n```bash\nnpx @n0zer0d4y/mercury-spec-ops\n```\n\n## Usage\n\n### Integration with MCP Clients\n\nConfigure the server in your MCP client (Claude Desktop, Cursor, etc.):\n\n#### Using npx (Recommended - No Installation)\n\n**For Claude Desktop** (`claude_desktop_config.json`):\n\n```json\n{\n  \"mcpServers\": {\n    \"mercury-spec-ops\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@n0zer0d4y/mercury-spec-ops\"]\n    }\n  }\n}\n```\n\n**For Cursor** (`~/.cursor/mcp.json`):\n\n```json\n{\n  \"mcpServers\": {\n    \"mercury-spec-ops\": {\n      \"timeout\": 60,\n      \"type\": \"stdio\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@n0zer0d4y/mercury-spec-ops\"]\n    }\n  }\n}\n```\n\n#### Using Local Installation\n\n**For Claude Desktop** (`claude_desktop_config.json`):\n\n```json\n{\n  \"mcpServers\": {\n    \"mercury-spec-ops\": {\n      \"command\": \"node\",\n      \"args\": [\"/path/to/mercury-spec-ops/dist/src/server.js\"]\n    }\n  }\n}\n```\n\n**For Cursor** (`~/.cursor/mcp.json`):\n\n```json\n{\n  \"mcpServers\": {\n    \"mercury-spec-ops\": {\n      \"timeout\": 60,\n      \"type\": \"stdio\",\n      \"command\": \"node\",\n      \"args\": [\"/path/to/mercury-spec-ops/dist/src/server.js\"]\n    }\n  }\n}\n```\n\n**Windows Local Path Example** (Cursor):\n\n```json\n{\n  \"mcpServers\": {\n    \"mercury-spec-ops\": {\n      \"timeout\": 60,\n      \"type\": \"stdio\",\n      \"command\": \"node\",\n      \"args\": [\n        \"C:\\\\Development\\\\Projects\\\\MCP-Servers\\\\mercury-spec-ops\\\\dist\\\\src\\\\server.js\"\n      ]\n    }\n  }\n}\n```\n\n**Important Notes:**\n\n- **npx**: Automatically fetches the latest version from npm (recommended for most users)\n- **Local**: Replace the path with your actual project location and run `npm run build` first\n- **Restart**: Restart your MCP client after configuration changes\n\n## Workflow Examples\n\n### Example 1: Enhanced Codebase Analysis\n\n1. **User Prompt**: \"Analyze this Node.js/TypeScript codebase focusing on security and performance\"\n2. **Claude Desktop Action**:\n   - Calls the `codebase-analysis-prompt` with technology_stack: \"node.js,typescript\" and analysis_focus: \"security,performance\"\n   - System programmatically assembles: base prompt + Node.js module + TypeScript module + security module + performance module\n   - The prompt instructs Claude to first read the `resource://codebase-analysis-template`\n   - Template builder assembles: base template + Node.js sections + TypeScript sections + security sections + performance sections\n   - Claude reads the dynamically assembled template\n   - Claude analyzes the codebase and generates a comprehensive technology-specific report\n\n### Example 2: Enhanced Bug Analysis\n\n1. **User Prompt**: \"Analyze this critical security bug in React application\"\n2. **Claude Desktop Action**:\n   - Calls the `bug-analysis-prompt` with technology_stack: \"react\", severity_level: \"critical\", and bug_type: \"security\"\n   - System assembles: base prompt + React module + security module + critical severity module\n   - Template includes: general sections + React-specific + security-specific + critical-severity sections\n   - Claude reads the bug analysis template\n   - Claude analyzes the bug and generates a comprehensive technology and severity-specific report\n\n### Example 3: PRD Generation with Technology Support\n\n1. **User Prompt**: \"Help me create a PRD for a React-based task management application\"\n2. **Claude Desktop Action**:\n   - Calls the `prd-prompt` with project details and technology_stack: \"react\"\n   - System assembles: base prompt + React module\n   - Template builder includes: base PRD template + React-specific considerations\n   - Claude reads the technology-enhanced PRD template\n   - Claude generates a comprehensive PRD with React-specific sections\n\n## Prompt Details\n\n### PRD Prompt\n\n- **Name**: `prd-prompt`\n- **Arguments**:\n  - `project_name` (required): Name of the software project\n  - `project_description` (required): Brief description of the project\n  - `target_audience` (optional): Target audience for the product (enum values)\n  - `project_type` (optional): Type of project (enum values)\n  - `key_features` (optional): Key features to include in the PRD\n  - `technology_stack` (optional): Technology stack to be used (enum values)\n  - `custom_instructions` (optional): Custom instructions for PRD generation\n\n### Codebase Analysis Prompt\n\n- **Name**: `codebase-analysis-prompt`\n- **Arguments**:\n  - `repository_path` (required): Path to the repository to analyze\n  - `technology_stack` (required): Technology stack used in the codebase (enum values)\n  - `analysis_focus` (optional): Focus areas for analysis (enum values)\n  - `custom_instructions` (optional): Custom instructions for codebase analysis\n\n### Bug Analysis Prompt\n\n- **Name**: `bug-analysis-prompt`\n- **Arguments**:\n  - `repository_path` (required): Path to the repository with bugs to analyze\n  - `bug_description` (required): Description of the bug or issue to analyze\n  - `affected_components` (optional): Components affected by the bug\n  - `severity_level` (optional): Severity level of the bug (enum values)\n  - `bug_type` (optional): Type of bug (enum values)\n  - `technology_stack` (optional): Technology stack used in the affected components (enum values)\n  - `custom_instructions` (optional): Custom instructions for bug analysis\n\n## Resource Details\n\n### PRD Template\n\n- **URI**: `resource://prd-template`\n- **Format**: Markdown\n- **Content**: Modular PRD template with technology-specific sections that dynamically assemble based on input parameters\n\n### Codebase Analysis Template\n\n- **URI**: `resource://codebase-analysis-template`\n- **Format**: Markdown\n- **Content**: Modular codebase analysis template with technology and focus-specific sections that assemble based on analysis parameters\n\n### Bug Analysis Template\n\n- **URI**: `resource://bug-analysis-template`\n- **Format**: Markdown\n- **Content**: Modular bug analysis template with severity and technology-specific sections that assemble based on bug parameters\n\n## Development\n\n### Project Structure\n\n```\nsrc/\n├── server.ts                    # Main MCP server implementation\n├── types/\n│   ├── enums.ts                 # All enum definitions (31 tech + 10 focus)\n│   └── index.ts                 # Type definitions and exports\n├── prompts/\n│   ├── modules/                 # 45 modular prompt components\n│   │   ├── technology/          # 31 technology-specific modules\n│   │   │   ├── languages/       # 11 language modules\n│   │   │   ├── runtimes/        # 1 runtime module\n│   │   │   ├── frameworks/      # 10 framework modules (3 frontend, 7 backend)\n│   │   │   ├── databases/       # 4 database modules\n│   │   │   ├── cloud/           # 3 cloud platform modules\n│   │   │   └── tools/           # 2 DevOps tool modules\n│   │   ├── analysis-focus/      # 10 focus-area modules\n│   │   └── bug-severity/        # 4 severity-specific modules\n│   ├── base-prompts/            # Base prompt templates\n│   └── prompt-builder.ts        # Programmatic prompt assembly\n├── resources/\n│   ├── templates/               # Modular template components\n│   │   ├── prd/                 # 10 PRD template modules\n│   │   ├── codebase-analysis/   # 8 codebase analysis modules\n│   │   └── bug-analysis/        # 4 bug analysis modules\n│   └── template-builder.ts      # Programmatic template assembly\n└── __tests__/                   # Comprehensive test suite (66 tests)\n    ├── utils/                   # Utility function tests (enum parser)\n    ├── prompts/                 # Prompt builder tests\n    ├── resources/               # Template builder tests\n    └── types/                   # Enum and type tests\n```\n\n### Testing\n\nThe project includes a comprehensive test suite with 88% coverage:\n\n```bash\n# Run all tests\nnpm test\n\n# Run tests in watch mode\nnpm run test:watch\n\n# Run tests with coverage report\nnpm run test:coverage\n\n# Run tests with interactive UI\nnpm run test:ui\n\n# Test MCP integration\nnpm run test:mcp\n```\n\n**Test Statistics**:\n\n- 66 tests (100% passing)\n- 88.48% overall coverage\n- Statement coverage: 88.48%\n- Line coverage: 88.70%\n\n### Building for Production\n\n```bash\nnpm run build\n```\n\n### Linting\n\n```bash\nnpm run lint\n```\n\n## Extending the System\n\n### Adding New Technology Modules\n\n1. Add the technology to the `TechnologyStack` enum in `src/types/enums.ts`\n2. Create a new module file in the appropriate category:\n   - Languages: `src/prompts/modules/technology/languages/`\n   - Frameworks: `src/prompts/modules/technology/frameworks/frontend/` or `backend/`\n   - Databases: `src/prompts/modules/technology/databases/`\n   - Cloud: `src/prompts/modules/technology/cloud/`\n   - Tools: `src/prompts/modules/technology/tools/`\n3. Implement the `TechnologyPromptModule` interface\n4. Export from the category's `index.ts`\n5. Register it in `prompt-builder.ts`\n6. Add corresponding template sections in `src/resources/templates/`\n7. Write tests in `src/__tests__/`\n\n### Adding New Focus Areas\n\n1. Add the focus area to the `AnalysisFocus` enum in `src/types/enums.ts`\n2. Create a new module file in `src/prompts/modules/analysis-focus/`\n3. Implement the `AnalysisFocusPromptModule` interface\n4. Export from `analysis-focus/index.ts`\n5. Register it in `prompt-builder.ts`\n6. Add corresponding template sections\n7. Write tests\n\n### Adding New Severity Levels\n\n1. Add the severity to the `BugSeverity` enum in `src/types/enums.ts`\n2. Create a new module file in `src/prompts/modules/bug-severity/`\n3. Implement the `BugSeverityPromptModule` interface\n4. Register it in the prompt builder\n5. Add corresponding template sections\n6. Write tests\n\n## Contributing\n\nContributions are welcome! Please follow these guidelines:\n\n- Fork the repository and create a feature branch\n- Follow existing code patterns and maintain test coverage above 85%\n- Use [Conventional Commits](https://www.conventionalcommits.org/) format (feat, fix, docs, test, chore)\n- Ensure all tests pass before submitting a pull request\n- See [Extending the System](#extending-the-system) for adding new modules\n\nReport issues on [GitHub Issues](https://github.com/n0zer0d4y/mercury-spec-ops/issues) with clear reproduction steps.\n\n## License\n\nThis project is licensed under the MIT License - see [LICENSE](LICENSE) file for details.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fn0zer0d4y%2Fmercury-spec-ops","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fn0zer0d4y%2Fmercury-spec-ops","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fn0zer0d4y%2Fmercury-spec-ops/lists"}