home / mcp / bmad mcp server

BMAD MCP Server

Breakthrough Method for Agile Ai Driven Development MCP Server

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "cexll-bmad-mcp-server": {
      "command": "bmad-mcp",
      "args": [],
      "env": {
        "BMAD_ENV": "YOUR_VALUE"
      }
    }
  }
}

BMAD-MCP is a lightweight workflow orchestrator that runs the complete agile development process as a MCP server. It coordinates each stage from Product Owner through QA, handles interactive clarification, saves artifacts, and integrates role-specific prompts and multiple engines to produce consistent, high-quality outputs.

How to use

You use BMAD-MCP by connecting it to an MCP client (Claude Code) and starting a BMAD workflow for your project. Start a session, choose the engines you want to run for the PO and Architect stages, and let BMAD-MCP guide the process through Requirement analysis, Architecture design, Sprint planning, development, review, and QA. You interact at key decision points: answer clarification questions, confirm generation results, and, during development, explicitly state the scope of work to execute.

Typical workflow sequence you follow: - Start a new BMAD session for your project objective - BMAD-MCP generates the Product Requirements Document (PRD) and System Architecture with interactive Q&A - BMAD-MCP creates a Sprint Plan and, when approved, moves into development - Development, code review, and QA are handled by Codex MCP at the appropriate stages - Artifacts and final documents are saved for traceability and review

How to install

Prerequisites: you need Node.js and npm installed on your system. You also need access to Claude Code to connect the BMAD-MCP server.

Install BMAD-MCP globally and configure Claude Code to use it.

# Step 1: Install BMAD-MCP globally
npm install -g bmad-mcp

# Step 2: Add BMAD-MCP to Claude Code (stdio backend)
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

Configuration and usage notes

BMAD-MCP uses a standard stdio MCP configuration for local operation. The server is started via a simple command, and Claude Code loads this configuration to run the workflow.

{
  "mcpServers": {
    "bmad": {
      "type": "stdio",
      "command": "bmad-mcp"
    }
  }
}

Advanced usage patterns

If you want to use dual engines at the PO/Architect stages, you can enable Codex alongside Claude. BMAD-MCP will merge results and select the best score, with fallback rules when scores are below the threshold. Interactive clarification questions help narrow gaps and drive regeneration until a score of 90 or higher is achieved.

During the SM stage, only Claude is used. For Dev/Review/QA stages, Codex MCP handles the code tasks. Ensure you use the correct model for code tasks: model: gpt-5 with sandbox: danger-full-access and approval-policy: on-failure.

File structure and artifacts

Your project contains a dedicated BMAD workflow directory that stores session state, task mappings, and temporary artifacts. Artifacts for each stage are saved to the corresponding .claude/specs paths and temporary files under .bmad-task/temp.

Troubleshooting tips

If the BMAD-MCP server does not start, verify the binary is available and try running it directly. If you see tool name errors, ensure you are using the correct tool names (e.g., bmad-task) in your integration code. Check session permissions and paths if a session cannot be found.

Security and best practices

Keep your environment secure by restricting access to your Claude Code workspace and BMAD-MCP server. Use least-privilege permissions for session directories and ensure artifact files are stored in a controlled location. Regularly review prompts and role configurations to maintain quality gates and prevent scope creep.

Notes on tooling and integration

BMAD-MCP integrates with Claude Code and Codex MCP to execute the full agile lifecycle. You interact with a single orchestrator that manages prompts, engine calls, artifact generation, and stage transitions.

Available tools

bmad-task

Orchestrates the BMAD-MCP workflow by starting, submitting, confirming stages, answering clarification questions, and querying status.

claude

Runs role prompts and generates outputs for PO and Architect stages as part of the integrated workflow.

codex

Provides code-focused tasks for Dev/Review/QA stages and integrates with Codex MCP for code generation and analysis.