Spec-Driven Development MCP server: prompts for spec-first work
Spec-Driven Development MCP Server
Three MCP prompts walk an agent from EARS-style requirements to a design document and then to application code
- 439 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The client runs an npm package through `npx`, and with the `@latest` tag a fresh version is fetched at every start
- The prompts ask the agent to create files in the `specs` folder and write code into the project root
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/spec-driven-development-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The client runs an npm package through `npx`, and with the `@latest` tag a fresh version is fetched at every start
- The prompts ask the agent to create files in the `specs` folder and write code into the project root
This is third-party code. Review the repository files before installing.
What it does
The MCP server gives an agent three prompts for specification-first development. The first turns a high-level description of an application into a `requirements.md` file in EARS (Easy Approach to Requirements Syntax) format, the second builds `design.md` from it, and the third writes code from that design. Requirements and design live in the project's `specs` folder, so you can read and edit them between steps. The third prompt asks for the code to go into the root folder. The server stores only the prompt texts: the agent itself creates and saves the files in your project. The project's own example description for the first prompt is a Vue.js todo application with task creation, completion tracking and local storage persistence. After that you call the two remaining prompts in order.
Who it is for. For developers working in Cursor, Claude Code or VS Code who want the agent to produce requirements and design documents first and code only after them.
Good fit when
- You are starting a small application from scratch and want requirements in EARS format before the first line of code
- You need a readable `design.md` that a colleague can review and you can edit by hand before code generation
- You want to try the requirements, design, code approach on a pilot project without installing a command set such as Spec Kit
- Your team already keeps documents in a `specs` folder and wants ready-made prompts for that layout
Not a fit when
- You need to drive changes in a large existing repository: the prompts assume an empty `specs` folder and the project root
- You require a check that the code matches the specification: the server does not provide one
- You need tasks, epics and tracker sync: toolkits such as Spec Kit cover that
- Your client does not show MCP prompts: without them the server offers nothing
Example request
Run the `generate-requirements` prompt for a Vue.js todo application with local storage persistence and show me what ended up in `specs/requirements.md`MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Each prompt is a one-sentence assignment, so the quality of the documents depends on the model and on how thoroughly you described the application. The agent judges for itself whether the design matches the requirements and the code matches the design: there are no automated checks.
Paths are set in the prompts themselves: requirements and design go into the `specs` folder and code into the project root. For an existing repository with its own layout you will have to state the root in your request.
Node.js 20 or newer is required to run it. The repository has not been updated since September 2025.
How to disable. Remove the `spec-driven` block from `mcp.json` and restart the client. Files the agent created in the `specs` folder stay in the project, so delete them by hand if you no longer need them.
FAQ
How do I install Spec-Driven Development MCP in Cursor or Claude Code?
Add a `mcpServers` block to `mcp.json` with a `spec-driven` server: command `npx`, arguments `-y` and `mcp-server-spec-driven-development@latest`. Cursor also has a one-click install button. Node.js 20 or newer is required.
Which prompts does the server provide?
Three: `generate-requirements` takes an application description and writes `specs/requirements.md`, `generate-design-from-requirements` reads the requirements and writes `specs/design.md`, and `generate-code-from-design` reads the design and writes code into the project root.
What is the EARS format?
It is a template for phrasing requirements: each one is written to a fixed pattern, which makes it easier to check. The first prompt asks the agent to write `requirements.md` in this format.
Does the server work in VS Code?
Yes. VS Code and VS Code Insiders have install buttons, and by hand you add the block to `mcp.json` under the `servers` key.
How is this different from Spec Kit?
Spec Kit puts a whole set of commands and skills into the project through a CLI. This is three MCP prompts with no CLI and no extra files in the project until the agent creates the documents.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for spec-driven development: requirements, design and tasks step by step, with a web dashboard and a VS Code extension
A plugin with skills for building TypeScript MCP servers and MCP apps: the agent scaffolds, edits, debugs and verifies them
Spec-driven development for coding agents: proposal, requirements, design and tasks come before any code
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A CLI that builds a ready-made TypeScript MCP server from an OpenAPI 3 spec, with tools, validation and auth generated for you
An MCP server that lets an agent read files, search code and run commands in a workspace
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Spec-Driven Development MCP server: prompts for spec-first work (this entry) | no | not required | 439 | |
| Spec Kit | no | 143,709 | a GitHub toolkit with the specify CLI that installs spec-driven commands and skills into a project | |
| OpenSpec | no | 73,280 | a workflow of proposal, requirements and design for coding agents | |
| cc-sdd | no | 3,746 | a Kiro-style skill set that takes a task from idea through requirements to code |
README in short
The description gathers install buttons for VS Code, VS Code Insiders and Cursor, and spells out the inputs and outputs of each prompt separately. At the end the author links to his article on why specification-driven development is worth adopting.