$git clone https://github.com/formulahendry/mcp-server-spec-driven-developmentModel Context Protocol (MCP) server that facilitates spec-driven development workflows by providing structured prompts for generating requirements, design documents, and code following a systematic approach.
| 1 | # Spec-Driven Development MCP Server |
| 2 | |
| 3 | [ |
| 4 | ](https://www.npmjs.com/package/mcp-server-spec-driven-development) [-VS_Code-0098FF)](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522spec-driven%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522mcp-server-spec-driven-development%2540latest%2522%255D%257D) |
| 5 | |
| 6 | Model Context Protocol (MCP) server that facilitates spec-driven development workflows by providing structured prompts for generating requirements, design documents, and code following a systematic approach. |
| 7 | |
| 8 | <a href="https://glama.ai/mcp/servers/@formulahendry/mcp-server-spec-driven-development"> |
| 9 | <img width="380" height="200" src="https://glama.ai/mcp/servers/@formulahendry/mcp-server-spec-driven-development/badge" alt="Spec-Driven Development Server MCP server" /> |
| 10 | </a> |
| 11 | |
| 12 | ## 🎯 Purpose |
| 13 | |
| 14 | This MCP server enables developers to follow a structured spec-driven development approach by providing prompts that guide you through: |
| 15 | |
| 16 | 1. **Requirements Generation** - Create detailed requirements documents using the EARS (Easy Approach to Requirements Syntax) format |
| 17 | 2. **Design Generation** - Generate design documents based on requirements |
| 18 | 3. **Code Generation** - Generate implementation code based on design documents |
| 19 | |
| 20 | ## ✨ Features |
| 21 | |
| 22 | - **Structured Workflow**: Follows a clear progression from **requirements** → **design** → **code** |
| 23 | - **EARS Format Support**: Uses industry-standard EARS format for requirements documentation |
| 24 | - **MCP Protocol**: Integrates seamlessly with MCP-compatible tools and environments |
| 25 | |
| 26 | ## 🚀 Quick Start |
| 27 | |
| 28 | ### Prerequisites |
| 29 | |
| 30 | - Node.js 20+ |
| 31 | |
| 32 | ### Installation |
| 33 | |
| 34 | #### VS Code |
| 35 | |
| 36 | Install the MCP server in VS Code using below buttons: |
| 37 | |
| 38 | [-VS_Code-0098FF)](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522spec-driven%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522mcp-server-spec-driven-development%2540latest%2522%255D%257D) [-VS_Code_Insiders-24bfa5)](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522spec-driven%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522mcp-server-spec-driven-development%2540latest%2522%255D%257D) |
| 39 | |
| 40 | Alternatively, you can add configuration in `mcp.json`: |
| 41 | |
| 42 | ```json |
| 43 | { |
| 44 | "servers": { |
| 45 | "spec-driven": { |
| 46 | "command": "npx", |
| 47 | "args": [ |
| 48 | "-y", |
| 49 | "mcp-server-spec-driven-development@latest" |
| 50 | ] |
| 51 | } |
| 52 | } |
| 53 | } |
| 54 | ``` |
| 55 | |
| 56 | #### Cursor, Claude Code |
| 57 | |
| 58 | Install the MCP server in Cursor using below button: |
| 59 | |
| 60 | [](https://cursor.com/install-mcp?name=spec-driven&config=JTdCJTIyY29tbWFuZCUyMiUzQSUyMm5weCUyMC15JTIwbWNwLXNlcnZlci1zcGVjLWRyaXZlbi1kZXZlbG9wbWVudCU0MGxhdGVzdCUyMiU3RA%3D%3D) |
| 61 | |
| 62 | Alternatively, you can add configuration in `mcp.json`: |
| 63 | |
| 64 | ```json |
| 65 | { |
| 66 | "mcpServers": { |
| 67 | "spec-driven": { |
| 68 | "command": "npx", |
| 69 | "args": [ |
| 70 | "-y", |
| 71 | "mcp-server-spec-driven-development@latest" |
| 72 | ] |
| 73 | } |
| 74 | } |
| 75 | } |
| 76 | ``` |
| 77 | |
| 78 | ## 📋 Available Prompts |
| 79 | |
| 80 | ### 1. Generate Requirements Document |
| 81 | - **Name**: `generate-requirements` |
| 82 | - **Description**: Generate requirements.md using EARS format |
| 83 | - **Input**: High-level requirements of the application. Example: 'A Vue.js todo application with task creation, completion tracking, and local storage persistence' |
| 84 | - **Output**: Structured requirements document in `specs/requirements.md` |
| 85 | |
| 86 | ### 2. Generate Design from Requirements |
| 87 | - **Name**: `g |