# spec-driven-development

This MCP server guides an agent from requirements to a design document and implementation code. Use it to give a project a written specification before code generation.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 438
- Author: formulahendry
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/formulahendry/mcp-server-spec-driven-development
- Updated: 2025-09-26
- HTML: https://affpapa.org/en/nevibecode/mcp/spec-driven-development

## What it does

The server provides three prompts for a staged workflow: generate requirements in EARS format, create a design from those requirements, then generate code from the design. The steps use `specs/requirements.md` and `specs/design.md`; implementation code goes in the project root.

Each stage reads the document produced by the previous one, so start with requirements generation. Node.js 20+ is required to run the server with the documented setup. Without that runtime, the `npx` installation command cannot launch it.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add spec-driven-development -- npx -y mcp-server-spec-driven-development
```

### Codex

**Platform CLI**
```bash
codex mcp add spec-driven-development -- npx -y mcp-server-spec-driven-development
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "spec-driven-development": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-server-spec-driven-development"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "spec-driven-development": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "mcp-server-spec-driven-development"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add spec-driven-development npx -y mcp-server-spec-driven-development
```

## When to use it
- write requirements in EARS format
- derive a design document from project requirements
- generate implementation code from a design document
- keep requirements, design, and code in a staged workflow

## Example prompts
- Use `generate-requirements` to draft EARS requirements for this project.
- Run `generate-design-from-requirements` using `specs/requirements.md`.
- Use `generate-code-from-design` to build from `specs/design.md`.

## Similar
- [Reactive Resume](https://affpapa.org/en/nevibecode/mcp/reactive-resume.md) — MCP server · ★ 44874
- [Sui Knowledge Base (kapa.ai)](https://affpapa.org/en/nevibecode/mcp/sui-knowledge-base-kapaai.md) — MCP server · ★ 7784
- [Claude Code Ultimate Guide](https://affpapa.org/en/nevibecode/mcp/claude-code-ultimate-guide.md) — MCP server · ★ 6237
- [Zotero MCP](https://affpapa.org/en/nevibecode/mcp/zotero-mcp.md) — MCP server · ★ 5548
- [RevoGrid DataGrid MCP Pro](https://affpapa.org/en/nevibecode/mcp/revogrid-datagrid-mcp-pro.md) — MCP server · ★ 3450
- [Claude Code Explorer MCP](https://affpapa.org/en/nevibecode/mcp/codeaashu-claude-code-explorer-mcp.md) — MCP server · ★ 3409

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md