Spec Kit MCP Server
Related Servers
Alternatives to Spec Kit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables specification-driven development workflows for AI editors by managing structured project specifications through stages like requirements, design, and tasks.25 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables spec-driven development workflows with AI assistants, providing tools for managing specification lifecycles, task dependencies, code navigation, testing, and automated reviews through a unified CLI and MCP interface.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to drive spec-driven development through slash-command workflows for planning, exploring, implementing, updating, and finalizing changes, with local daemon and project registry support.464,552 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents like Claude Code and Cursor to self-onboard a project by running spec-driven development setup from within the editor, inferring answers from the repo and prompting only for what remains. It initializes and manages a .specs/ directory over HTTP with no install or API key.1,242 npm38MIT
- AlicenseBqualityCmaintenanceConnects OpenSpec specification system to AI coding assistants, enabling automated spec-driven development workflows.1137 npm2MIT

SpecDown MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceGives AI assistants direct read/write access to SpecDown Markdown spec documents, enabling spec-driven development without copy-pasting.11 npm3MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose in the spec-kit workflow: constitution (principles), plan (technical plan), specify (description), tasks (task list), and implement (execution). There is no overlap or ambiguity between these stages, making tool selection straightforward for an agent.
All tool names follow a consistent 'speckit_' prefix with a descriptive action suffix (e.g., constitution, implement, plan, specify, tasks). This uniform pattern enhances readability and predictability across the toolset.
With 5 tools, the server is well-scoped for its purpose of project specification and implementation. Each tool represents a distinct phase in the workflow, and the count is neither too sparse nor excessive for the domain.
The toolset provides complete coverage of the spec-kit lifecycle, from establishing principles (constitution) and planning to specifying, task generation, and implementation. There are no obvious gaps, and the tools logically progress through the project development stages.