BMAD-MCP is a lightweight workflow orchestrator that manages the complete agile development process through multiple stages - from Product Owner to Quality Assurance. It manages workflow state, dispatches role-specific prompts, and saves development artifacts, working seamlessly with Claude Code to execute the entire software development lifecycle.
# Step 1: Install globally from npm
npm install -g bmad-mcp
# Step 2: Add to Claude Code
claude mcp add-json --scope user bmad '{"type":"stdio","command":"bmad-mcp"}'
# Step 3: Verify installation
bmad-mcp
# Expected output: "BMAD MCP Server running on stdio"
That's it! Restart Claude Code and you're ready to use the BMAD workflow.
npm install -g bmad-mcp
claude mcp add-json --scope user bmad '{"type":"stdio","command":"bmad-mcp"}'
git clone https://github.com/cexll/bmad-mcp-server
cd bmad-mcp-server
npm install
npm run build
npm link # Makes bmad-mcp globally available
# Add to Claude Code
claude mcp add-json --scope user bmad '{"type":"stdio","command":"bmad-mcp"}'
# Check if binary is available
which bmad-mcp
# Output: /usr/local/bin/bmad-mcp (or similar)
# Test the server directly
bmad-mcp
# Expected output: "BMAD MCP Server running on stdio"
# Press Ctrl+C to exit
# Restart Claude Code to load the configuration
# Remove from Claude Code
claude mcp remove bmad
# Uninstall npm package
npm uninstall -g bmad-mcp
Simply tell Claude Code to use BMAD:
User: Use bmad-task to create a user authentication system
Claude Code will:
All artifacts are saved to: .claude/specs/user-authentication-system/
MCP configuration is automatically added to ~/.claude/config.json:
{
"mcpServers": {
"bmad": {
"type": "stdio",
"command": "bmad-mcp"
}
}
}
| Stage | Role | Engines | Description |
|---|---|---|---|
| PO | Product Owner | Claude + Codex | Requirements analysis (merge both) |
| Architect | System Architect | Claude + Codex | Technical design (merge both) |
| SM | Scrum Master | Claude | Sprint planning |
| Dev | Developer | Codex | Code implementation |
| Review | Code Reviewer | Codex | Code review |
| QA | QA Engineer | Codex | Testing and quality assurance |
// 1. Start workflow
const startResult = await callTool("bmad-task", {
action: "start",
cwd: "/path/to/your/project",
objective: "Implement user login system"
});
const { session_id, task_name, role_prompt, engines } = JSON.parse(startResult.content[0].text);
// 2. Execute with engines
if (engines.includes("claude")) {
const claudeResult = await callClaude(role_prompt);
}
if (engines.includes("codex")) {
const codexResult = await callCodexMCP(role_prompt);
}
// 3. Submit results
await callTool("bmad-task", {
action: "submit",
session_id: session_id,
stage: "po",
claude_result: claudeResult,
codex_result: codexResult
});
// 4. Confirm and proceed (unified: saves + advances to next stage)
await callTool("bmad-task", {
action: "confirm",
session_id: session_id,
confirmed: true
});
{
"action": "start",
"cwd": "/path/to/project",
"objective": "Project description"
}
{
"action": "submit",
"session_id": "uuid",
"stage": "po",
"claude_result": "...",
"codex_result": "..."
}
{
"action": "confirm",
"session_id": "uuid",
"confirmed": true
}
{
"action": "answer",
"session_id": "uuid",
"answers": ["Answer to Q1", "Answer to Q2"]
}
{
"action": "approve",
"session_id": "uuid",
"sprint_selection": "all" // or "1" for just Sprint 1
}
Important - Dev Stage Behavior:
{
"action": "status",
"session_id": "uuid"
}
your-project/
├── .bmad-task/
│ ├── session-abc-123.json # Workflow state (with content references)
│ ├── task-mapping.json # Maps session_id → task_name
│ └── temp/
│ └── abc-123/ # Temporary content files
│ ├── po_claude_result_xxx.md
│ ├── po_codex_result_xxx.md
│ └── po_final_result_xxx.md
├── .claude/
│ └── specs/
│ └── implement-user-login/ # Task name (human-readable slug)
│ ├── 01-product-requirements.md
│ ├── 02-system-architecture.md
│ ├── 03-sprint-plan.md
│ ├── 04-dev-reviewed.md
│ └── 05-qa-report.md
└── src/
Default: Only Claude (single engine)
Dual Engine: Enabled when objective contains "codex" or "使用 codex"
If dual engine enabled:
Interactive Clarification:
# Check global installation
which bmad-mcp
# Verify npm global installation path
npm config get prefix
# Reinstall if needed
npm uninstall -g bmad-mcp
npm install -g bmad-mcp
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "bmad" '{"type":"stdio","command":"bmad-mcp"}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"bmad": {
"type": "stdio",
"command": "bmad-mcp"
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"bmad": {
"type": "stdio",
"command": "bmad-mcp"
}
}
}3. Restart Claude Desktop for the changes to take effect