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
      318 PyPI
      Business Source 1.1

    • Agent Harness Kit

      Ngoc7225
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT

    • Spec-Tools-MCP

      blue03183
      A
      license
      Not graded
      quality
      B
      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.
      454 npm
      1
      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

    C2.2/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools map to distinct SDD workflow phases, but boundaries blur between artifact submission (sdd-design, sdd-tasks, sdd-requirements), validation (sdd-validate-design, sdd-validate-gap, sdd-quality-check), and governance actions (sdd-approve, sdd-review-test-cases, sdd-spec-impl). Descriptions help, but an agent could plausibly misselect among the validate/check/review tools.

    Naming Consistency2/5

    The sdd- prefix is consistent, but the remainder mixes verb-first, noun-first, and bare-noun conventions: sdd-validate-design vs sdd-context-load vs sdd-design. This makes the set feel inconsistent even though each name is individually readable.

    Tool Count3/5

    17 tools is borderline heavy for an SDD workflow server. The surface is large enough that governance, validation, artifact submission, and progress tracking each contribute multiple tools, risking cognitive load for agents selecting the right operation.

    Completeness4/5

    The lifecycle is broadly covered from init through requirements, design, tasks, implementation, quality checks, approval, and status. Minor gaps remain around reading or updating existing artifacts beyond submission and approval, plus no clear reset/delete path for features.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources