Spec Kit MCP Server
# Spec Kit MCP Server
This is a Model Context Protocol (MCP) server for [Spec Kit](https://github.com/github/spec-kit). It allows AI assistants to interact with Spec Kit templates and workflows directly to help manage project specifications, planning, and implementation.
## Prerequisites
Before using this MCP server, you must have `specify-cli` installed on your system.
### Persistent Installation (Recommended)
Install once and use everywhere:
```bash
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
```
Then use the tool directly:
```bash
specify init <PROJECT_NAME>
specify check
```
To upgrade Specify, see the Upgrade Guide for detailed instructions. Quick upgrade:
```bash
uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git
```
## Installation & Usage
### Using with MCP Clients (e.g., Claude Desktop, Cursor)
You can run this server directly using `npx`. Add the following configuration to your MCP client settings:
```json
{
"mcpServers": {
"spec-kit": {
"command": "npx",
"args": [
"-y",
"@anyicode/spec-kit-mcp@latest"
]
}
}
}
```
## Features
This server provides prompts and tools to guide the AI through the Spec Kit workflow:
* **Constitution** (`speckit.constitution`): Establish or review project principles (code quality, testing, etc.).
* **Specify** (`speckit.specify`): Combine templates with user requirements to describe what to build.
* **Plan** (`speckit.plan`): Analyze the project and create a technical plan.
* **Tasks** (`speckit.tasks`): Break down the plan into actionable tasks.
* **Implement** (`speckit.implement`): Provide implementation guidelines.
The server automatically detects and uses the `commands/` directory in your project root to access these templates.
## Publishing
To release a new version of this package, follow these steps:
1. Update the package version (e.g., patch, minor, major):
```bash
npm version patch
```
2. Build the project:
```bash
npm run build
```
3. Publish the package to npm:
```bash
npm publish --access public
```
4. Verify the package is published:
```bash
npm view @anyicode/spec-kit-mcp
```
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose in the spec-kit workflow: constitution (principles), plan (technical plan), specify (description), tasks (task list), and implement (execution). There is no overlap or ambiguity between these stages, making tool selection straightforward for an agent.
All tool names follow a consistent 'speckit_' prefix with a descriptive action suffix (e.g., constitution, implement, plan, specify, tasks). This uniform pattern enhances readability and predictability across the toolset.
With 5 tools, the server is well-scoped for its purpose of project specification and implementation. Each tool represents a distinct phase in the workflow, and the count is neither too sparse nor excessive for the domain.
The toolset provides complete coverage of the spec-kit lifecycle, from establishing principles (constitution) and planning to specifying, task generation, and implementation. There are no obvious gaps, and the tools logically progress through the project development stages.