F
licenseNot graded
qualityB
maintenanceOrchestrates multi-stakeholder feature refinement and development execution workflows for AI-assisted software teams.
-
BMAD-MCP
by cexll
Related Servers
Alternatives to BMAD-MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceOrchestrates multiple AI agents (Product Manager, Software Architect, Engineer, QA, Reviewer) to collaboratively plan, design, implement, review, and improve software development projects via MCP tools.13-
- AlicenseNot gradedqualityDmaintenanceCoordinates specialized agents (Architecture, Quality, Cloud, Prompt) to plan, build, test, and deploy applications with self-healing capabilities, authentication, and analytics for autonomous software engineering workflows.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides a specification-driven workflow layer for AI-assisted coding, enabling agents to follow an explicit 11-phase feature workflow with checkpoints, artifacts, and quality gates.MIT
- AlicenseAqualityAmaintenanceOrchestrates multiple AI coding agents declaratively to automate software development workflows for engineering teams.1231,431 PyPI1,286Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides an AI-driven four-stage software development workflow with role management, enabling structured requirements analysis, design, implementation, and testing.1MIT
TDQS
B3.2/5.0
Scored across 1 tool
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness2/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues