Spec-Driven MCP Server
Enables specification-driven development workflows for AI editors by managing structured project specifications through stages like requirements, design, and tasks.
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<br>⢠Generate all .spec/*.md file content<br>⢠Make technical routing decisions based on complexity assessment<br>⢠Process user requirements into structured requirements_prompt |
| š¤ User | Requirement Owner & Quality Controller | ⢠Clearly express desired features and functionality<br>⢠Review generated documentation to ensure it meets actual requirements<br>⢠Control workflow progress (continue/restart/modify)<br>⢠Provide project context that influences implementation decisions |
| š§ Tool | Workflow Orchestrator | ⢠Automatically detect current stage and manage requirements ā design ā tasks progression<br>⢠Validate workflow dependencies before stage transitions<br>⢠Provide structured prompts for LLM content creation<br>⢠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 build
License
MIT License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.