BMAD-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bmad-taskB | BMAD (Business-Minded Agile Development) workflow orchestrator. Manages complete development workflow: PO → Architect → SM → Dev → Review → QA. Key features:
This tool returns:
It does NOT call LLMs directly - that's Claude Code's responsibility. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'bmad-task' has a clearly defined purpose as a workflow orchestrator, so agents cannot misselect between multiple options.
A single tool inherently has perfect naming consistency. The tool name 'bmad-task' follows a clear pattern (server_prefix-function), and with no other tools to compare against, there are no inconsistencies in naming conventions.
A single tool is generally too few for a server claiming to manage a complete development workflow with multiple stages (PO, Architect, SM, Dev, Review, QA). While the tool is described as an orchestrator, the lack of specialized tools for different workflow stages or operations suggests an under-scoped surface for the apparent domain.
The tool surface is severely incomplete for a workflow orchestrator domain. There are no tools for specific operations like creating tasks, updating statuses, managing artifacts directly, or handling approvals—only a single orchestrator tool. This will likely cause agent failures when trying to perform granular workflow actions.