bmad-mcp-server

Load embedded BMAD files on-demand (configs, agents, workflows, tasks, etc.). Use this tool to retrieve the content of files from the embedded BMAD resources. All files are relative to the embedded directory. Common paths: - Config: core/config.yaml - Agents: core/agents/bmad-master.md, bmm/agents/analyst.md - Workflows: core/workflows/party-mode/workflow.yaml - Workflow instructions: core/workflows/party-mode/instructions.md - Tasks: core/tasks/workflow.xml Note: _cfg/ manifest files are excluded - use bmad_manifest() instead. Args: path: Relative path within the embedded directory (e.g., "core/config.yaml") Returns: Content of the requested file, or an error message if the file doesn't exist

Load a BMad task definition. If no name provided, lists all available tasks from the manifest. Otherwise loads the specified task file. Args: name: Task name or path (or None to list all) Returns: Task content or list of available tasks

Load a BMad workflow definition. If no name provided, lists all available workflows from the manifest. Otherwise loads the specified workflow YAML configuration. Common workflows: - party-mode (Multi-agent group discussion) - brainstorming (Brainstorming sessions) - bmad-init (Initialize BMad in workspace) Args: name: Workflow name or path (or None to list all) Returns: Workflow YAML content or list of available workflows

Main BMad interface with smart command parsing. Intelligently routes commands to appropriate handlers: - Agent names → loads agent (analyst, architect, dev, pm, sm, tea, ux-expert) - Workflow names → loads workflow (party-mode, brainstorming, etc.) - Commands → executes (list-workflows, list-tasks, list-agents) - Default → loads master agent Examples: bmad() → Load master agent bmad("analyst") → Load analyst agent bmad("party-mode") → Load party-mode workflow bmad("list-workflows") → List all workflows bmad("brainstorming") → Load brainstorming workflow Args: command: Agent name, workflow name, or command (default: "master") user_name: Your name for personalized interactions language: Preferred communication language Returns: JSON response with instructions and files, or command result

Load a BMad agent persona. If no name provided, lists all available agents from the manifest. Otherwise loads the specified agent with injected user preferences. Available agents (when manifest is loaded): - master / bmad-master (Master orchestrator) - analyst (Business Analyst) - architect (System Architect) - dev (Developer) - pm (Product Manager) - sm (Scrum Master) - tea (Test Architect) - ux-expert (UX Expert) Args: name: Agent name from manifest (or None to list all) user_name: Your name for personalized interactions language: Preferred communication language Returns: JSON with agent instructions and available files, or list of agents

Load BMad manifest files from the current workspace or embedded resources. Manifests list available resources. First attempts to load from workspace, falls back to embedded manifests. Args: type: Type of manifest to load (agent, workflow, task, file) Returns: Manifest content in CSV format or error message

Load BMad configuration files. If no path provided, returns the main config file (core/config.yaml). Specify a path to load a different config file. Available configs: - core/config.yaml (main configuration) - bmm/config.yaml (BMM module configuration) Args: path: Optional path to specific config file Returns: Configuration file content in YAML format