Spec-Driven Development

The Spec-Driven Development MCP Server facilitates a structured development workflow through a series of prompts. These prompts generate requirements, design documents, and then code.

The MCP server guides developers through a distinct three-step process. It begins with the definition of requirements via the EARS format, proceeds to the creation of a design document, and concludes with the generation of implementation code from that design.

This methodology establishes a traceable path from concept to product, which promotes consistency and helps teams meet project goals.

Installation

To use this MCP server, you should add its configuration to the mcp.json file in your project’s root directory. The MCP client reads this file to find and manage available servers.

{
    "servers": {
        "spec-driven": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-server-spec-driven-development@latest"
            ]
        }
    }
}

This configuration tells the MCP client to create a server named spec-driven. It uses npx to download and run the mcp-server-spec-driven-development package on demand.

Available Prompts

The server’s workflow is built around three core prompts:

1. Generate Requirements Document (generate-requirements)

• Description: Generates a requirements.md file with the EARS format.
• Input: A high-level text description of the application’s requirements. For example: ‘A Vue.js todo application with task creation, completion tracking, and local storage persistence’.
• Output: Creates a structured requirements document at specs/requirements.md.

2. Generate Design from Requirements (generate-design-from-requirements)

• Description: Generates a design.md file from the requirements.
• Input: Reads directly from the specs/requirements.md file.
• Output: Creates a design document at specs/design.md.

3. Generate Code from Design (generate-code-from-design)

• Description: Generates implementation code from the design document.
• Input: Reads directly from the specs/design.md file.
• Output: Places the generated implementation code in the project’s root folder.

You should run these prompts in order. This creates a clear and traceable path from the initial idea to the final code.

FAQs

Q: What is the EARS format?
A: EARS, or Easy Approach to Requirements Syntax, is a notation that structures requirement statements to reduce ambiguity. It uses specific keywords to define the conditions under which a system must perform an action. This server uses it to generate requirements that are clear, concise, and testable.

Q: Can I modify the generated documents or code?
A: Yes. The generated files (requirements.md, design.md, and the source code) are starting points. You can and should edit them to refine the details. The quality of the final output is directly influenced by the clarity of your initial requirements and any manual adjustments you make to the design document before you generate the code.

Q: What programming languages and frameworks does it support?
A: The server is language-agnostic. Its ability to generate specific code depends on the instructions inside the design document. If your design.md specifies a Python application with the Flask framework, it will attempt to generate that. The more detailed your design document, the more accurate the resulting code will be for your chosen tech stack.