🛠️ Spec-Kit Plus MCP Server
MCP (Model Context Protocol) server that wraps Spec-Kit Plus tools so any AI IDE or CLI (Qwen, Gemini, Claude Code, Cursor, etc.) can use it globally.
📦 What This Is
This MCP server acts as a bridge between AI agents and the Spec-Kit Plus CLI (specifyplus), enabling spec-driven development workflows across any MCP-compatible AI tool.
User (in any AI IDE/CLI)
│
▼
MCP Protocol
│
▼
speckit-plus-mcp/
server.py ← MCP Server
│
▼
specifyplus CLI ← Spec-Kit Plus (sp init, sp.plan, sp.tasks, etc.)
✅ Prerequisites
# Install specifyplus (the CLI being wrapped)
pip install specifyplus
# Install MCP Python SDK
pip install "mcp[cli]"
🚀 Installation
-
Clone or download this repository
-
Install dependencies:
cd speckit-plus-mcp pip install -e .
-
Configure your AI agent (see below)
🔧 Configuration
Qwen CLI
Create ~/.qwen/settings.json:
{
"mcpServers": {
"speckit-plus": {
"command": "python",
"args": ["/ABSOLUTE/PATH/TO/speckit-plus-mcp/server.py"],
"env": {
"PYTHONPATH": "."
}
}
}
}
⚠️ Replace
/ABSOLUTE/PATH/TO/with your actual path.
Gemini CLI
Create ~/.gemini/settings.json:
{
"mcpServers": {
"speckit-plus": {
"command": "python",
"args": ["/ABSOLUTE/PATH/TO/speckit-plus-mcp/server.py"]
}
}
}
Claude Code
Create ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"speckit-plus": {
"command": "python",
"args": ["/ABSOLUTE/PATH/TO/speckit-plus-mcp/server.py"]
}
}
}
Cursor / VS Code (with MCP extension)
Add to .cursor/mcp.json inside your project:
{
"mcpServers": {
"speckit-plus": {
"command": "python",
"args": ["/ABSOLUTE/PATH/TO/speckit-plus-mcp/server.py"]
}
}
}
🧪 Testing
Test the server runs correctly:
cd speckit-plus-mcp
python server.py
You should see: Running MCP server 'speckit-plus'
Test inside Qwen CLI:
qwen
Then type /mcp — you should see:
speckit-plus: CONNECTED
Tools: speckit_init, speckit_check, speckit_specify, speckit_plan ...
📋 Available Tools
| Tool | Description |
|---|---|
speckit_init |
Initialize a new Spec-Kit Plus project for any AI agent |
speckit_check |
Verify all required tools are installed |
speckit_constitution |
Set project governing principles |
speckit_specify |
Write requirements specification (WHAT to build) |
speckit_clarify |
Run structured clarification before planning |
speckit_plan |
Generate technical plan with tech stack (HOW to build) |
speckit_tasks |
Break plan into ordered task list |
speckit_implement |
Execute all tasks to build the full project |
speckit_workflow_guide |
Get complete step-by-step workflow instructions |
📘 Usage Example
In your AI agent (Qwen, Claude, etc.):
Use speckit_init to create a project called "todo-app" for qwen,
then show me the workflow guide.
Complete Workflow:
-
Initialize project:
speckit_init(project_name="my-app", ai_agent="qwen") -
Set principles:
/sp.constitution Enforce clean code, testing, and performance -
Write specification:
/sp.specify Build a task manager with Kanban boards and user assignments -
Clarify gaps (recommended):
/sp.clarify -
Technical plan:
/sp.plan Use FastAPI, PostgreSQL, React, Docker -
Generate tasks:
/sp.tasks -
Build the project:
/sp.implement
🎯 Supported AI Agents
- qwen
- claude
- gemini
- copilot
- cursor
- windsurf
- opencode
- codex
- amp
📁 Output Files
After running the workflow, you'll find these files in .specify/:
.specify/
├── memory/
│ └── constitution.md ← Your project principles
└── specs/
└── 001-feature/
├── spec.md ← Requirements & user stories
├── plan.md ← Technical implementation plan
├── tasks.md ← Ordered task list
└── data-model.md ← Database schema
🏗️ How It Works
AI Agent (Qwen/Gemini/Claude)
│
│ speaks MCP protocol
▼
server.py (MCP server)
│
│ calls subprocess
▼
specifyplus CLI (sp commands)
│
│ reads/writes
▼
.specify/ folder
(spec.md, plan.md, tasks.md)
│
│ used by
▼
AI Agent builds the project
MCP = Model Context Protocol — a standard that lets any AI agent talk to any tool server. This server.py IS the bridge between the AI and Spec-Kit Plus.
📄 License
MIT
Metadata
Release files for speckit-plus-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| speckit_plus_mcp-0.1.0.tar.gz | 8.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| speckit_plus_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.5 kB
Release files / speckit_plus_mcp-0.1.0.tar.gz
| Download URL | speckit_plus_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9706ecd7d4945448f7546ede901c53b8087cc5d05415bbc871d1bcdba9b056ea
|
|
BLAKE2b-256 checksum How to use checksums |
4796493feb5ddba7e47ba053536f7f9ce3b73bf1e698682d3241e66d29e45e45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / speckit_plus_mcp-0.1.0-py3-none-any.whl
| Download URL | speckit_plus_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28e117f95ea6d246e40fac87acec77a1ee1af8f98db5ec280283ebdb0893af7d
|
|
BLAKE2b-256 checksum How to use checksums |
67f22d6682d1b547c135313981b4a07543d29a8161707d9c66b74cf4ceef48e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for speckit-plus-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.