This MCP server provides an AI-guided spec-driven development workflow that systematically transforms ideas into implementation through five structured stages: Goal Collection → Requirements Gathering → Design Documentation → Task Planning → Task Execution.
Core Capabilities:
Define and confirm feature goals - Articulate high-level objectives with specific feature naming
Gather detailed requirements - Generate structured, testable requirements in EARS format (Easy Approach to Requirements Syntax)
Create technical design documentation - Develop comprehensive architecture, data models, component designs, and API specifications
Plan executable tasks - Decompose features into prioritized, manageable implementation tasks with dependencies
Execute tasks systematically - Implement code with step-by-step guidance and optional task-specific execution
Generate structured documentation - Automatically produce organized
requirements.md,design.md, andtasks.mdfiles in standardized project structure (docs/specs/{feature_name}/)Manage development sessions - Track progress through the workflow with session IDs and confirmation steps between phases
The server enforces a disciplined methodology using proven templates, ensuring clear requirements, better design decisions, and more maintainable code. Available as both a Claude Code Skill (no setup) and MCP server for Claude Desktop, Cursor, and other MCP-compatible IDEs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Spec-driven Development MCP Serverhelp me build a user profile page with avatar upload"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Spec-driven Development Workflow
An AI-guided spec-driven development workflow available as both a Claude Code Skill and MCP Server. Transform your development process with structured, step-by-step guidance from idea to implementation.
What is Spec-driven Development?
Spec-driven development is a methodology that emphasizes creating detailed specifications before writing code. This approach helps ensure clear requirements, better design decisions, and more maintainable code. This workflow guides you through the process with AI assistance.
🎯 Two Ways to Use This Workflow
Option 1: Claude Code Skill (Recommended for Claude Code Users)
Simple, integrated, no setup required!
The workflow is available as a native Claude Code Skill. Just invoke it in any conversation:
Or naturally:
Benefits:
✅ No installation or configuration needed
✅ Native integration with Claude Code
✅ Seamless conversation flow
✅ Automatic progress tracking with TodoWrite
Learn more: Skill Documentation | Migration Guide
Option 2: MCP Server (For Other IDEs)
Use as an MCP server for Claude Desktop, Cursor, or other MCP-compatible tools.
Installation via Smithery:
Learn more: See MCP Server Setup below.
Features
Complete Development Workflow: From goal collection to task execution
AI-Powered Guidance: Step-by-step instructions for each development phase
Structured Documentation: Generates organized specs in EARS format
Template-Based: Uses proven templates for requirements, design, and tasks
MCP Server Setup
This section is for users who want to use the workflow as an MCP server (Option 2 above).
Installation
Installing via Smithery
To install spec-coding-mcp for Claude Desktop automatically via Smithery:
Using npx (Recommended)
Using npm
Usage
With Cursor
Add to your Cursor MCP settings:
Available Tools
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
Workflow Stages & Example
The spec-driven development process follows five distinct stages. Here's how it works with a real example - building a user authentication feature:
1. Goal Collection - Define What You Want to Build
Purpose: Establish clear, specific objectives for your feature.
Example Interaction:
2. Requirements Gathering - Create Detailed EARS-format Requirements
Purpose: Transform your goals into specific, testable requirements using the EARS (Easy Approach to Requirements Syntax) format.
Example Interaction:
3. Design Documentation - Technical Architecture and Design
Purpose: Create detailed technical specifications including architecture, component design, data models, and API specifications.
Example Interaction:
4. Task Planning - Break Down into Executable Tasks
Purpose: Decompose the feature into specific, prioritized development tasks with clear dependencies.
Example Interaction:
5. Task Execution - Implement the Code
Purpose: Execute the planned tasks systematically, implementing the feature according to specifications.
Example Interaction:
Generated Project Structure
Throughout the workflow, the following documentation structure is created:
Development
Prerequisites
Make sure you have Node.js 18+ installed.
Setup
Running the Project
Publishing
To publish the package to npm:
Contributing & License
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT
Attribution
This project was inspired by and builds upon concepts from vibedevtools by @yinwm, a collection of development efficiency tools.