multi-agent-mcp
Related Servers
Alternatives to multi-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceTransforms AI agents into spec-driven product engineers by managing the software project lifecycle through requirements, design, implementation, and archiving phases with state-aware MCP tools.4 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables collaborative software development through a team of specialized AI agents (Architect, Developer, Reviewer, Tester) communicating via the Model Context Protocol, with tools for file management, task tracking, and code review.-
- FlicenseNot gradedqualityDmaintenanceEnables users to generate complete, production-ready software projects from simple ideas by coordinating 8 specialized AI agents through the Model Context Protocol.4-
- AlicenseNot gradedqualityCmaintenanceA reusable AI software development team built on MCP. 13 specialized agents (Project Manager, Backend, Frontend, QA, Security, DevOps, UX, and more) collaborate via shared SQLite state. Exposes 44 MCP tools across 12 domains. All discussions and decisions are stored in the database so agents get back up to speed immediately when re-loaded.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to use GitHub Projects v2 as a shared task substrate, with registration, atomic task checkout, heartbeats, budgets, peer review, and self-healing coordination. It also automates PRD-to-issue pipelines, sprint planning, triage, roadmaps, GitHub Actions, releases, and branch workflows through MCP tools, resources, and prompts.35 npmMIT
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.1412 npm14MIT
TDQS
Scored across 13 tools
Most tools target distinct roles and phases, but review_code and suggest_improvements both analyze code for quality, and analyze_codebase overlaps with review activities. The boundaries are clear enough that agents can select correctly with minor caution.
Strong verb_noun pattern for most tools (plan_feature, design_architecture, implement_code, etc.), but collaborate is just a verb and full_workflow uses an adjective_noun form. The outliers are readable and not confusing, just less consistent.
13 tools is well-scoped for a multi-agent development workflow covering planning, architecture, implementation, review, testing, estimation, collaboration, and session management. Each tool clearly earns its place.
The surface covers the core development lifecycle end-to-end, including a full_workflow orchestrator and session history management. Minor gaps exist around explicit session creation or non-destructive session deletion, but agents can work around them.