bmad

BMAD MCP Server provides centralized access to the BMAD methodology, offering 11 specialized agents and 36+ automated workflows that you can invoke from any MCP-compatible client. Use the unified bmad tool to list agents, read agent details, and execute agents or workflows with natural language prompts or structured messages. The server also supports multi-source content loading and BMAD URIs to retrieve resources, enabling consistent collaboration across projects. In practice, you can ask your AI assistant to run a PRD workflow, fetch the system architecture for a design review, or have an agent like Mary analyze market opportunities, all through the MCP protocol.

To operate, you typically issue MCP operations such as { operation: "list", query: "agents" } to discover available agents, then read details with { operation: "read", type: "agent", agent: "analyst" }, and finally execute with { operation: "execute", agent: "analyst", message: "Help me..." } or a workflow like { operation: "execute", workflow: "prd", message: "Create PRD for a task management app" }. Your client configuration points to the bmad MCP server (via npx in this setup); you can also configure multi-source loading, custom BMAD_ROOT, or Git remotes to fetch content from additional repositories. The result is a consistent, install-once, widely-usable interface for BMAD across your projects.

Prerequisites:

• Node.js 18 or later installed on the host
• An MCP-compatible client (e.g., Claude Desktop, VS Code with Copilot, Cline, etc.)

Installation options:

Option 1: npx (Recommended)

• This runs the server on demand via npx from the npm registry.

Configure in your MCP client:

{
  "mcpServers": {
    "bmad": {
      "command": "npx",
      "args": ["-y", "bmad-mcp-server"]
    }
  }
}

Option 2: Global Installation

• Install the package globally and run via the global command:

npm install -g bmad-mcp-server

Configure in your MCP client:

{
  "mcpServers": {
    "bmad": {
      "command": "bmad-mcp-server"
    }
  }
}

Option 3: Local Development

• Clone the repo, install, build, and run locally:

git clone https://github.com/mkellerman/bmad-mcp-server.git
cd bmad-mcp-server
npm install
npm run build

Configure in your MCP client with the local build path:

{
  "mcpServers": {
    "bmad": {
      "command": "node",
      "args": ["/absolute/path/to/bmad-mcp-server/build/index.js"]
    }
  }
}

Client-specific setup (examples):

• Claude Desktop, VS Code Copilot, Cline, etc., typically use the same npx or package-based configuration shown above.

Notes and tips:

• The server discovers BMAD content in this order: project-local ./bmad/, user-global ~/.bmad/, Git remotes cloned to ~/.bmad/cache/git/, and finally package defaults. If you run into missing content, verify these locations.
• You can use multi-source loading by appending a Git remote URL to the npx command, enabling shared content across team members. -BMAD_ROOT can customize the project root for BMAD content if you’re hosting multiple BMAD-enabled projects.
• If you encounter port or network issues, ensure your MCP client can access the server binary (via npx or local path) and that any firewall rules allow the process to start.
• The server exposes tools, resources, prompts, and completions via the bmad URIs scheme for BMAD content access.