spec-kit

This MCP server exposes the complete Spec-Kit workflow as a JSON-RPC 2.0 compatible service. It provides 10 tools that cover the entire spec-driven development lifecycle, from initializing a project to validating and refining implementation. You can run the server via the npx method (which downloads the latest prebuilt binary on first use) or install it locally through Cargo for a faster startup. Once running, connected AI agents or editors can invoke the tools through the MCP protocol, enabling automated project setup, constitutions, requirements, planning, task generation, implementation, clarifications, analysis, and checklist generation. The tools are designed to be composable: for example, you can initialize a project with speckit_init, then iterate by using speckit_plan and speckit_tasks to break work down, followed by speckit_implement to generate scaffolding, and speckit_check to validate readiness before review with speckit_checklist. The server is built with Rust and Tokio for high-performance asynchronous I/O and provides strict type safety and validation for tool inputs and outputs.

Prerequisites:

• Rust toolchain (for Cargo installation)
• Node.js 18+ (if you plan to use the npx method)
• Git (for cloning or fetching sources as needed)
• Optional: uv/uvx setup if you prefer running Spec-Kit via the UV runtime (per Spec-Kit prerequisites)

Install via Cargo (recommended for offline reliability):

cargo install spec-kit-mcp

Install via npm/npx (no local install required):

# Global install (optional, if you want a persistent binary)
npm install -g @lsendel/spec-kit-mcp

# Or run directly with npx (downloads on first use)
npx -y @lsendel/spec-kit-mcp

Configure your MCP client (example for Claude Code):

{
  "mcpServers": {
    "spec-kit": {
      "command": "npx",
      "args": ["-y", "@lsendel/spec-kit-mcp"],
      "env": {}
    }
  }
}

Verify installation by running the server and querying the available tools (tool names are documented under Available Tools in the repository).

Tips and common issues:

• The Spec-Kit MCP server exposes 10 tools; ensure your client lists all 10 to confirm a healthy integration: speckit_init, speckit_constitution, speckit_specify, speckit_plan, speckit_tasks, speckit_implement, speckit_clarify, speckit_analyze, speckit_check, speckit_checklist.
• If using the npx method, the first invocation may be slower due to binary download; subsequent runs are fast.
• Environment variables can be used to customize tool behavior if the server exposes such options; start with an empty env block and add entries as needed (VAR_NAME: description).
• If tools do not appear in your editor after startup, verify the MCP config path, validate JSON syntax, and check editor logs for errors.
• The server relies on GitHub Spec-Kit via uvx at runtime when using the provided prerequisites; ensure network access and git capabilities are available if you use the Git-based workflow.