spec-driven-mcp
v0.1.0
Published
A Model Context Protocol (MCP) server that provides structured project specification management capabilities for AI editors through a specification-driven development workflow
Maintainers
Readme
Spec-Driven MCP Server
A Model Context Protocol (MCP) server that provides structured project specification management capabilities for AI editors through a specification-driven development workflow.
Features
- Specification-Driven Development: Kiro Spec-driven development for any AI tool that supports MCP
Usage
Build a TODO Web app like Microsoft Todo, using Spec-driven development mode
Build a TODO Web app like Microsoft Todo, using Spec-driven development mode, just want the requirements and tasks stage, and then complete the workflow.
Tools
init_spec_project
Initialize the specification-driven project structure and templates.
Purpose: Create the foundational directory structure and template files required for specification-driven development.
Features:
- Creates
.spec/and.spec/template/directories - Copies default template files for requirements, design, and tasks
- Idempotent operation (can be safely run multiple times)
- Prepares workspace for subsequent specification generation
Parameters: No parameters required
create_spec
Start a specification-driven development workflow.
Parameters:
requirements_prompt(string, optional): User requirement description. Required for requirements stage. Used to convert user requirements into structured specifications.stage(enum, optional): Jump directly to specified stage ("requirements", "design", "tasks"). If not specified, automatically detects current stage.next_stage(enum, optional): Specify next stage after completion ("design", "tasks", null). Allows LLM to intelligently choose workflow path based on requirement complexity.
Workflow Stages:
- Requirements: Analyze and document functional requirements
- Design: Create technical architecture and implementation approach
- Tasks: Break down implementation into actionable development tasks
Usage Patterns:
- Complex features:
requirements → design → tasks - Simple features:
requirements → tasks(skip design) - Documentation only:
requirements → complete
Responsibility Matrix
| Role | Core Position | Primary Responsibilities | |------|---------------|-------------------------| | 🤖 LLM | Intelligent Analyzer & Decision Maker | • Analyze requirement complexity and infer next_stage values• Generate all .spec/*.md file content• Make technical routing decisions based on complexity assessment• Process user requirements into structured requirements_prompt | | 👤 User | Requirement Owner & Quality Controller | • Clearly express desired features and functionality• Review generated documentation to ensure it meets actual requirements• Control workflow progress (continue/restart/modify)• Provide project context that influences implementation decisions | | 🔧 Tool | Workflow Orchestrator | • Automatically detect current stage and manage requirements → design → tasks progression• Validate workflow dependencies before stage transitions• Provide structured prompts for LLM content creation• Provide clear guidance when dependencies are missing or parameters are invalid |
Installation & Setup
It is not recommended to install this as a global MCP tool. Please install it in your workspace.
Claude Desktop
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"spec-driven": {
"command": "npx",
"args": ["-y", "spec-driven-mcp"],
"env": {
"SPEC_ROOT_DIR": "/path/to/workspace"
}
}
}
}VS Code / Cursor
Add the following to your .cursor/mcp.json or VS Code MCP settings:
{
"mcpServers": {
"spec-driven": {
"command": "npx",
"args": ["-y", "spec-driven-mcp"],
"env": {
"SPEC_ROOT_DIR": "/path/to/workspace"
}
}
}
}Template Customization
Edit template files in the .spec/template/ directory to customize the generated specification format. Each call to create_spec uses the latest template version to generate specification prompts.
Template Files:
requirements.md: User story format with acceptance criteriadesign.md: Architecture design including component relationshipstasks.md: Implementation checklist with specific actionable tasks
Development
pnpm watch # Development mode with auto-reload
pnpm build # Production buildLicense
MIT License
