GenSpec MCP Server

MCP server for GenSpec workflow - converts USER-STORIES.md into README, ROADMAP, and SYSTEM-ARCHITECTURE documents. Exposed over MCP by the genspec mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that converts user stories into structured documentation including README, ROADMAP, and SYSTEM-ARCHITECTURE documents through a guided approval workflow.

GenSpec MCP Server streamlines the documentation creation process by taking user stories as input and generating three key documentation artifacts:

• MCP Integration — - Works seamlessly with Claude Desktop, VS Code with MCP extension, and Cursor
• Template-Based Generation — - Uses predefined templates for consistent documentation structure
• Approval Workflow — - Generate → Present → Approve/Edit cycle for each document
• Phase Dependencies — - ROADMAP requires README, SYSTEM-ARCHITECTURE requires both
• Multiple Entry Points — - Start from any phase or run the complete workflow
• Resource Access — - Exposes templates via MCP resource protocol

Its toolset

Everything the assistant can do here goes through one of these:

• start_genspec — Run full workflow: README → ROADMAP → SYSTEM-ARCHITECTURE
• generate_readme — Generate README, then continue through ROADMAP → SYSTEM-ARCHITECTURE
• generate_roadmap — Generate ROADMAP, then continue through SYSTEM-ARCHITECTURE
• generate_architecture — Generate only SYSTEM-ARCHITECTURE
• Prerequisites — The Prerequisites tool exposed by this server
• Cursor — The Cursor tool exposed by this server
• Building — The Building tool exposed by this server
• Debugging — Enable debug logging by setting the DEBUG environment variable:

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at genspec-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

• Node.js 18.0.0 or higher - npm or yarn package manager

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. GenSpec MCP's toolset — start_genspec, generate_readme, generate_roadmap and 5 more — is a fair guide to whether it matches your workflow. It is maintained by iamhenry; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against GenSpec MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the genspec mcp mcp server does with a few real requests.