Skip to main content
Glama

Related Servers

Alternatives to starter-doc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to generate structured PRDs, decompose epics into testable user stories, validate Given/When/Then acceptance criteria, and export markdown backlogs.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Facilitates spec-driven development workflows by providing structured prompts for generating requirements in EARS format, design documents, and implementation code following a systematic approach.
      67 npm
      440
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables a coding agent to keep one JSON feature specification per feature, governed by a progressive schema, and to render it as editable Markdown documents for a product owner. Answers and direct Markdown edits are reconciled back into the validated model through stdio MCP tools, applying coherent changes and reporting those that widen scope or contradict the model.
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to parse, create, update, delete, and search natural language specification elements in markdown files via MCP tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Spec-Driven Development toolkit that transforms LLMs into development agents by providing expert-crafted prompts for generating structured specifications and validating documents across the Requirements → Design → Tasks → Code workflow.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents to turn high-level features into structured PRDs, user stories, Gherkin acceptance criteria, edge cases, and OpenAPI-compatible API contract skeletons. It exposes MCP tools for synthesizing requirements and generating endpoint specifications.
      7
      MIT

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each generate_* tool targets a distinct, named artifact (SRS, PRD, ERD, SDD, DESIGN), and audit_spec_completeness and list_blueprint_templates serve clearly different roles. The only overlap is generate_full_blueprint, which subsumes all five document generators, so an agent must decide between the bundle and an atomic document — a real but well-documented ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (generate_srs, generate_prd, audit_spec_completeness, list_blueprint_templates). The one longer name, generate_full_blueprint, still fits the same pattern without breaking convention.

    Tool Count5/5

    Eight tools is well within the sweet spot for a documentation-generation server, with one generator per artifact plus a bundle, an auditor, and a template lister. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the full spec suite (PRD, SRS, ERD, SDD, DESIGN) plus audit and template discovery, which is strong lifecycle coverage for the stated purpose. Minor gaps: Traceability Matrix and Agent Instructions are only reachable via the full blueprint bundle, and there is no tool to revise or patch an existing document after an audit.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues