Skip to main content
Glama
yi-john-huang

MCP SDD Server

by yi-john-huang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP SDD Server

No user-submitted related servers found.

    Related Servers

    • speckitmcp

      jthom233
      A
      license
      A
      quality
      D
      maintenance
      MCP server that integrates GitHub Spec-Kit with AI coding agents to manage Spec-Driven Development workflows, including specification authoring, planning, task generation, and consistency analysis.
      13
      1
      MIT

    • trw-mcp

      wallter
      A
      license
      B
      quality
      B
      maintenance
      MCP server providing persistent engineering memory and spec-driven development workflows for AI coding agents, preserving learnings across sessions.
      41
      3,058 PyPI
      Business Source 1.1

    • Spec-Tools-MCP

      blue03183
      A
      license
      Not graded
      quality
      A
      maintenance
      Centralized MCP server for spec-driven AI agent workflows, enabling isolated feature management, task tracking, and implementation with handoff and archiving capabilities across multiple projects and developers.
      62 npm
      1
      MIT

    • io.github.ymxlx/polis-protocol

      ymxlx
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides a local-first control plane for coding agents, enabling task routing, contract management, and shared learning across multiple AI vendors via markdown files.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.5/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools map to distinct SDD phases, but sdd-implement and sdd-spec-impl could be confused as both relate to implementation, and sdd-steering vs sdd-steering-custom have overlapping purposes. The descriptions help but boundaries are not always crisp.

    Naming Consistency3/5

    All tools share the 'sdd-' prefix, but the structure is mixed: some are verb-led (sdd-approve, sdd-validate-design), some are noun-led (sdd-requirements, sdd-status), and sdd-spec-impl uses an abbreviation, so the pattern is readable but inconsistent.

    Tool Count3/5

    16 tools is slightly above the ideal 3-15 range, and several are highly specialized (sdd-context-load, sdd-template-render) that may not be used in every workflow, making the set feel a bit heavy for the domain.

    Completeness4/5

    The surface covers the full SDD lifecycle from init to implementation, including requirements, design, tasks, validation, quality, and steering. Minor gaps exist such as no general artifact update/review tool beyond test cases, but core workflows are well supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources