spec-coding

Spec-driven Development Workflow is available as an MCP server that you can run via npx to enable Claude Desktop, Cursor, or any MCP-compatible IDE to guide you through a structured, AI-assisted development process. The server exposes a sequence of tools that orchestrate a five-stage workflow: starting with goal collection, then requirements gathering in EARS format, followed by a design specification, task planning, and finally task execution. Available tools include: spec_coding_workflow_start, spec_coding_goal_confirmed, spec_coding_requirements_start, spec_coding_requirements_confirmed, spec_coding_design_start, spec_coding_design_confirmed, spec_coding_tasks_start, spec_coding_tasks_confirmed, and spec_coding_execute_start. When used with a client, these tools drive the interactive steps, generate structured docs under docs/specs/{feature_name}, and track progress. The workflow produces organized specifications (goals, requirements, design, and tasks) that you can review, adjust, and implement, ensuring a spec-first approach to feature development.

Prerequisites:

• Node.js 18+ installed (or ensure your environment supports npx)
• npm or pnpm for local development if desired

Installation steps:

1. Install and run via npx (recommended):

# Always fetch the latest version
npx spec-coding-mcp@latest

# Or simply, which will also fetch the latest
npx spec-coding-mcp

2. Optional: install for global use with npm (alternative):

npm install -g spec-coding-mcp
spec-coding-mcp

3. If you want to install through Smithery (for Claude Desktop integration), use:

npx -y @smithery/cli install @kevinlin/spec-coding-mcp --client claude

Prerequisites for Smithery-based setup are covered by the Smithery CLI installation process. After installation, you can run the MCP server via the commands shown above.

Tips and common considerations:

• Use the latest version to get new features and fixes: npx spec-coding-mcp@latest
• If you are integrating with Cursor or Claude Desktop, ensure your MCP client configuration references the correct command and arguments (as shown in the example mcp_config).
• The server generates documentation under docs/specs/{feature_name}/ with requirements.md, design.md, and tasks.md; you can customize or extend these docs locally.
• If you need custom environment settings (e.g., API keys, experiment toggles), add them under the env field in your MCP server configuration.
• For troubleshooting, check that your Node.js version supports the required ES features and that your network can access npm registries for pulling the latest package.
• This MCP server is designed to be invoked by MCP clients; it does not require a separate backend, but you may want to store generated specs in a versioned repo.