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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。