multi-agent-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_featureC | Product Manager analyzes requirements and creates a detailed feature plan with user stories, acceptance criteria, and success metrics |
| design_architectureC | Architect designs the system architecture, data models, APIs, and scalability approach |
| implement_codeC | Engineer implements the feature with clean, tested, production-ready code |
| review_codeC | QA Engineer performs comprehensive code review for bugs, security, edge cases, and test coverage |
| suggest_improvementsB | Code Reviewer suggests improvements for readability, maintainability, and performance |
| generate_testsC | Engineer generates comprehensive test suite for the provided code |
| estimate_effortC | Product Manager estimates story points and development time for a requirement |
| analyze_codebaseC | Analyze existing codebase structure, patterns, and quality metrics |
| collaborateC | Multi-agent collaboration where agents discuss a topic and reach consensus through multiple rounds |
| full_workflowB | Execute complete development workflow: planning → architecture → implementation → QA → review |
| get_conversation_historyC | Retrieve the multi-agent conversation history with optional filtering |
| clear_historyB | Clear the current session's conversation history |
| list_sessionsB | List all available conversation sessions |
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 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.