home / mcp / spec-driven development mcp server
Spec-Driven Development MCP Server, not just Vibe Coding
Configuration
View docs{
"mcpServers": {
"formulahendry-mcp-server-spec-driven-development": {
"command": "npx",
"args": [
"-y",
"mcp-server-spec-driven-development@latest"
]
}
}
}You use this Spec-Driven Development MCP Server to guide your work from requirements through design to implementation. It provides structured prompts that help you generate requirements in EARS format, create design documents from those requirements, and emit implementation code from the design, creating a clear, traceable development workflow.
You interact with the server through an MCP-compatible client. Start by creating or loading your requirements. Use the generate-requirements prompt to produce an EARS-formatted requirements document. Then generate a design document from those requirements with generate-design-from-requirements. Finally, generate the implementation code using generate-code-from-design. This sequence establishes a clear, auditable path from what you want to build to how you will build it.
Prerequisites: Node.js 20 or newer.
{
"mcpServers": {
"spec_driven": {
"command": "npx",
"args": ["-y", "mcp-server-spec-driven-development@latest"]
}
}
}The server exposes three prompts you can use in order: generate-requirements, generate-design-from-requirements, and generate-code-from-design. Use them to create a complete, end-to-end spec-driven workflow.
Generates a requirements document in EARS format from high-level inputs.
Creates a design document based on the generated requirements.
Produces implementation code from the design document.