Skip to main content
Glama
n0zer0d4y

Mercury Spec Ops MCP Server

by n0zer0d4y
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Mercury Spec Ops MCP Server

No user-submitted related servers found.

    Related Servers

    • Vibe-Coder-MCP

      fatma03281
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform software-development tasks such as deep research, codebase mapping, context curation, requirements and user-story generation, full-stack starter project scaffolding, and multi-step workflow execution.
      19 npm
      MIT

    • Vibe Coder MCP Server

      kohaku04
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to research, plan, and generate software requirements, user stories, task lists, starter projects, and codebase maps through specialized development tools. It also supports intelligent context curation, AI-native task management, and multi-step workflow execution.
      19 npm
      MIT

    • Vibe Coder MCP Server

      JoseWisniewski288
      A
      license
      Not graded
      quality
      A
      maintenance
      It equips AI assistants with specialized software development tools for research, planning, requirements generation, user story creation, project scaffolding, codebase analysis, context curation, task management, and multi-step workflow execution.
      19 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources