mcp-server-spec-driven-development and spec-coding-mcp
About mcp-server-spec-driven-development
formulahendry/mcp-server-spec-driven-development
Spec-Driven Development MCP Server, not just Vibe Coding
Implements a three-stage MCP workflow that chains requirements generation (EARS format) → design documents → code output, with each stage reading structured specs from the previous phase. Integrates directly into VS Code, Cursor, and Claude Code via npx installation, communicating through the Model Context Protocol to enable AI-assisted development from specification to implementation.
About spec-coding-mcp
feiyun0112/spec-coding-mcp
Transform feature ideas into production-ready code through systematic Spec-Driven Development 通过系统化的**规格驱动开发**，将功能想法转化为可投入生产的代码
An MCP server that integrates with AI IDEs (GitHub Copilot, etc.) to scaffold structured development workflows using three core specification documents: EARS-formatted requirements, technical design, and decomposed task lists. Operates as a .NET 10 service that guides multi-phase development from function definition through requirements collection, design review, task planning, and execution—materializing vague features into verifiable engineering processes rather than unstructured AI-assisted coding.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work