spec-driver-mcp
Spec Driver MCP is a Model Context Protocol server that enables structured, spec-driven AI development by guiding projects through a 3-phase workflow (Requirements → Design → Tasks) with approval gates and automation hooks.
Initialize a spec workspace (
init-spec): Set up a.spec/directory with config, default hooks, and support forfeatureorbugfixspec types usingrequirements-firstordesign-firstworkflows.Write spec documents (
write-spec-file): Create or update the three core spec files:requirements.md— User stories and acceptance criteriadesign.md— Architecture, components, and data flowtasks.md— Trackable checkbox task lists
Read spec documents (
read-spec-file): Retrieve the current content of any core spec file.List spec files (
list-spec-files): View the status of all spec files, including existence, size, task counts, and associated hooks.Track task progress (
update-task): Mark individual tasks as completed[x]or pending[ ]intasks.md, identified by line number or partial text match.Get task summary (
get-task-summary): Retrieve overall task completion statistics (completed vs. total tasks).Create automation hooks (
create-hook): Register event-driven rules that instruct the AI to automatically perform actions when specific workflow events occur (e.g., auto-mark tasks, validate phase transitions, sync docs on requirement changes).List hooks (
list-hooks): View all registered automation hooks, their trigger events, and descriptions.Delete hooks (
delete-hook): Remove a specific automation hook by name.Run hooks (
run-hooks): Execute all hooks associated with a specific event (e.g.,on-task-completed,on-spec-phase-change), enabling automated workflow enforcement at key development milestones.
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-driver-mcpanalyze my project and create a spec"
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 Driver MCP
A Model Context Protocol server that brings Kiro-style spec-driven development to any AI coding tool (Claude Code, Cursor, opencode, Codex CLI, Reasonix, Gemini CLI, and more).
What it does
Replaces unstructured chat with a 3-phase workflow when you ask AI to build, plan, or refactor a project:
Phase 1: Requirements → requirements.md (EARS format: WHEN...THE SYSTEM SHALL...)
Phase 2: Design → design.md (architecture, components, data flow)
Phase 3: Tasks → tasks.md (trackable [x] checkboxes)Each phase requires your approval before advancing. Hooks auto-maintain consistency.
Related MCP server: Spec-driven Development MCP Server
Quick Start
1. Install
npx github:linanwanttodo/spec-driver-mcpOr install globally:
npm install -g github:linanwanttodo/spec-driver-mcp2. Add to your AI tool
opencode
Add to ~/.config/opencode/opencode.json:
{
"mcp": {
"spec-driver": {
"type": "local",
"command": ["npx", "github:linanwanttodo/spec-driver-mcp"]
}
}
}Claude Code
Add to ~/.claude/settings.json:
{
"mcpServers": {
"spec-driver": {
"command": "npx",
"args": ["github:linanwanttodo/spec-driver-mcp"]
}
}
}Then copy instructions/CLAUDE.md to your project root as CLAUDE.md.
Cursor
Create .cursor/mcp.json in your project:
{
"mcpServers": {
"spec-driver": {
"command": "npx",
"args": ["github:linanwanttodo/spec-driver-mcp"]
}
}
}Then copy instructions/cursor-rules.md to your project root as .cursorrules.
Codex CLI
Add to ~/.codex/config.toml:
[mcp_servers.spec-driver]
command = "npx"
args = ["github:linanwanttodo/spec-driver-mcp"]Reasonix
Add to ~/.reasonix/config.json mcp array:
"spec-driver=npx github:linanwanttodo/spec-driver-mcp"Gemini CLI
Add to ~/.gemini/config/mcp_config.json:
{
"mcpServers": {
"spec-driver": {
"command": "npx",
"args": ["github:linanwanttodo/spec-driver-mcp"]
}
}
}Usage
Once configured, just tell your AI:
"帮我开发一个博客系统" or "帮我分析这个项目" or "我们来重构这个"
The AI will automatically:
Read your codebase to understand context
Ask you clarifying questions (requirements-first or design-first? specific details?)
Write requirements.md using EARS notation
Wait for your approval before proceeding
Write design.md with architecture and component design
Wait for your approval
Write tasks.md with
- [ ]checkboxesWait for your approval, then implement
Marking tasks done
During implementation:
- [x] Task completed via update-task
- [ ] Still pendingThe AI auto-runs hooks at each event:
on-task-completed→ auto-mark task [x], check acceptance criteriaon-spec-phase-change→ validate document completenesson-user-request-change→ sync all documents
Tools
Tool | Description |
| Initialize .spec/ with config + 3 default hooks |
| Write requirements.md / design.md / tasks.md |
| Read any spec file |
| Show file status + hooks |
| Toggle task [x] or [ ] |
| Task completion stats |
| Create automation rules |
| List all hooks |
| Remove a hook |
| Execute hooks for an event |
Spec File Location
All files are created in .spec/ at your project root:
your-project/
├── .spec/
│ ├── .config # Project metadata
│ ├── requirements.md # Phase 1: Requirements
│ ├── design.md # Phase 2: Design
│ ├── tasks.md # Phase 3: Tasks
│ └── hooks/ # Automation rules
│ ├── auto-mark-completed.md
│ ├── validate-before-phase.md
│ └── notify-on-change.md
├── ...your code...Default Hooks
Hook | Event | What it does |
|
| Auto update-task after implementation |
|
| Validate doc completeness before advancing |
|
| Sync all docs when requirements change |
One-Click AI Install Prompt
If you're asking an AI to set this up for you, copy this:
Install spec-driver-mcp from GitHub and configure it:
1. Run: npm install -g github:linanwanttodo/spec-driver-mcp
2. Add "spec-driver" to the MCP servers config of my AI tool
(the config format depends on which tool I use)
3. Done - no server needed, no API keys, no registrationLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/linanwanttodo/spec-driver-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server