bmad

BMAD-MCP is a lightweight workflow orchestrator that manages the complete agile development process as an MCP server. It coordinates the Product Owner, Architect, Scrum Master, Developer, Code Reviewer, and QA Engineer workflow, saving artifacts and guiding the lifecycle through stages such as PO, Architect, SM, Dev, Review, and QA. By default, it integrates Claude for natural language prompts and can use Codex for code-oriented tasks, enabling a blended engine approach when needed. The server exposes its prompts and context through Claude Code, which then executes the appropriate engines and submits results back to BMAD-MCP for merging, scoring, and progression to the next stage. This makes it suitable for structured, interactive requirement gathering, architecture planning, and artifact generation (PRDs, architecture diagrams, sprint plans, and more).

Prerequisites:

• Node.js and npm installed on your system
• Claude Code integration set up (as described in your Claude Code workflow)

Option A: Install via NPM (Recommended)

1. Install globally:

npm install -g bmad-mcp

2. Add to Claude Code so Claude can invoke BMAD:

claude mcp add-json --scope user bmad '{"type":"stdio","command":"bmad-mcp"}'

3. Verify installation:

bmad-mcp
# Expected output: "BMAD MCP Server running on stdio"

Option B: Build from Source

1. Clone the repository and install dependencies:

git clone https://github.com/cexll/bmad-mcp-server
cd bmad-mcp-server
npm install

2. Build and link locally:

npm run build
npm link  # Makes bmad-mcp globally available

3. Add to Claude Code:

claude mcp add-json --scope user bmad '{"type":"stdio","command":"bmad-mcp"}'

Verify installation:

which bmad-mcp
bmad-mcp
# Expected output: "BMAD MCP Server running on stdio"

Uninstall:

claude mcp remove bmad
npm uninstall -g bmad-mcp

Tips and caveats:

• The MCP config is typically loaded into Claude Code as shown in the Configuration Location section of the BMAD README. Ensure the bmad-mcp binary is in your PATH when using the stdio interface.
• BMAD supports multiple engines per stage (Claude, Codex) and will merge results, score artifacts, and advance stages automatically when you confirm.
• Artifacts and logs are stored per task under your Claude specs directory (e.g., .claude/specs/...); keep an eye on directories to locate generated PRDs, architecture docs, and sprint plans.
• If you encounter issues with engine availability, verify Claude Code integration and that the bmad-mcp command is accessible from the environment running Claude Code.
• The configuration shown uses stdio; if you switch to another interface later, adapt the mcpServers entry accordingly (e.g., for npx, node, or docker).