Spec-Driven Development MCP server

Transforms development from idea to implementation through structured phases including goal collection, EARS format requirements gathering, technical design documentation, task planning, and systematic code execution with template-based guidance and organized specification documents.
Back to servers
Setup instructions
Provider
Kevin Lin
Release date
Jul 31, 2025
Stats
14 stars

An MCP server that brings AI-guided spec-driven development workflow to any AI-powered IDEs. This tool transforms your development process with structured, step-by-step guidance from idea to implementation using a methodology that emphasizes creating detailed specifications before writing code.

Installation Options

Using npx (Recommended)

The simplest way to install and run the spec-coding-mcp server is using npx:

# Always get the latest version
npx spec-coding-mcp@latest

# Or simply (will also get latest)
npx spec-coding-mcp

Using npm

You can also install the package globally using npm:

npm install -g spec-coding-mcp
spec-coding-mcp

Installing via Smithery

To install spec-coding-mcp for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @kevinlin/spec-coding-mcp --client claude

Integrating with Cursor

Add the following to your Cursor MCP settings:

{
  "mcpServers": {
    "spec-coding-mcp": {
      "command": "npx",
      "args": ["spec-coding-mcp@latest"],
      "env": {},
      "disabled": false
    }
  }
}

Available Tools

The MCP server provides several tools that guide you through different stages of the development workflow:

  • spec_coding_workflow_start - Start the development workflow
  • spec_coding_goal_confirmed - Confirm feature goals
  • spec_coding_requirements_start - Begin requirements gathering
  • spec_coding_requirements_confirmed - Confirm requirements completion
  • spec_coding_design_start - Start design documentation
  • spec_coding_design_confirmed - Confirm design completion
  • spec_coding_tasks_start - Begin task planning
  • spec_coding_tasks_confirmed - Confirm task planning completion
  • spec_coding_execute_start - Start task execution

Development Workflow

The spec-driven development process follows five distinct stages:

Goal Collection

Define clear, specific objectives for your feature. For example:

User: I want to build a user authentication feature
Assistant: Let me start the spec-driven development workflow for you.
[calls spec_coding_workflow_start]

Let's define your feature goals:
1. What specific authentication methods do you want to support?
2. Do you need social login (Google, GitHub, etc.)?  
3. What user roles and permissions are required?

User: I need email/password login with JWT tokens, plus Google OAuth, and basic user/admin roles.

Requirements Gathering

Transform your goals into specific, testable requirements using the EARS (Easy Approach to Requirements Syntax) format:

Assistant: Great! Now let's gather detailed requirements.
[calls spec_coding_requirements_start]

[Assistant generates detailed EARS-format requirements]
- WHEN a user provides valid email/password THEN the system SHALL authenticate them
- GIVEN a user wants Google OAuth WHEN they click "Sign in with Google" THEN the system SHALL redirect to Google

Design Documentation

Create detailed technical specifications including architecture, component design, data models, and API specifications:

Assistant: Now let's create the technical design.
[calls spec_coding_design_start]

[Assistant creates detailed design document including:]
- Database schema for users, sessions, oauth_tokens
- Authentication middleware architecture  
- JWT token structure and validation flow

Task Planning

Decompose the feature into specific, prioritized development tasks with clear dependencies:

Assistant: Let's break this down into executable tasks.
[calls spec_coding_tasks_start]

[Assistant creates numbered task list:]
1. Set up database models (User, Session, OAuthToken)
2. Implement JWT token service
3. Create email/password authentication endpoints

Task Execution

Execute the planned tasks systematically, implementing the feature according to specifications:

Assistant: Time to implement! Let's start coding.
[calls spec_coding_execute_start]

[Assistant implements each task step by step]

Project Documentation Structure

Throughout the workflow, the following documentation structure is created:

docs/specs/{feature_name}/
├── requirements.md    # EARS-format requirements
├── design.md          # Technical architecture  
└── tasks.md           # Implementation checklist

This structured approach ensures your development process is methodical, well-documented, and produces high-quality, maintainable code.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "spec-driven-dev-mcp" '{"command":"npx","args":["spec-driven-dev-mcp@latest"],"env":[],"disabled":false}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "spec-driven-dev-mcp": {
            "command": "npx",
            "args": [
                "spec-driven-dev-mcp@latest"
            ],
            "env": [],
            "disabled": false
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "spec-driven-dev-mcp": {
            "command": "npx",
            "args": [
                "spec-driven-dev-mcp@latest"
            ],
            "env": [],
            "disabled": false
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later