CrossAgentMCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CrossAgentMCPstart a three-agent session to co-author a design doc"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CrossAgentMCP — an A2A pool MCP
A minimal implementation of the A2A.md vision: an A2A pool MCP where
any agent can register into the shared pool,
any agent can bind into a multi-agent session,
agents watch each other's activity, critique peers after they finish, self-improve, and keep working with no human intervention until a shared goal is satisfied by every agent in the session.
Architecture
Three process types:
┌────────────────── POOL (:9100, FastAPI HTTP JSON-RPC) ──────────────────┐
│ registry / sessions / activity / critique / goal (in-memory control │
│ plane — does NOT route work messages) │
└──────────────────────────────────────────────────────────────────────────┘
▲ pool JSON-RPC (PoolClient) ▲ pool JSON-RPC (per-agent bridge)
│ │
┌─────┴──────┐ peer A2A (SendMessage/GetTask) ┌─────┴──────┐
│ orchestrator│◄──────────────────────────────────►│ agent-N │ … :9101..9103
└────────────┘ each agent runs its own └────────────┘
headless v1.0 A2A HTTP serverPool (
crossagent/pool.py) — central control plane: registry, sessions, an append-only per-session activity log, critique threads, and per-agent satisfaction.Agents — each is a directory (
agents/<role>/) with:server.py— a v1.0 A2A HTTP server (peer data plane);.mcp.json— registers thea2astdio MCP bridge (crossagent/a2a_bridge.py);CLAUDE.md— the role + per-turn contract.
Orchestrator (
crossagent/orchestrator.py) — the only component that advances time: registers agents, creates the session, then round-robin runs each agent headlessly (claude -p), feeding it the activity/critique delta since its last turn, until all members are satisfied (or a turn budget / no-progress guard trips).
Related MCP server: kitty-hive
Protocol
Faithful to A2A v1.0 (PascalCase JSON-RPC methods, camelCase JSON,
SCREAMING_SNAKE_CASE enums). See crossagent/a2a.py.
Setup
uv sync # Python 3.11+ venv + depsUsage
make test # unit tests (protocol / pool / orchestrator with fake agents)
make smoke # pool + 2 A2A servers up; scripted round-trip (no real Claude)
make demo # full headless 3-agent demo (writer / critic / lead) — needs `claude`Demo goal
demo/goal.json asks three agents — writer, critic, lead — to co-author
demo/output/design.md (a URL-shortener design) until all three declare satisfied.
Notes
.mcp.jsonfiles hardcode the repo pathD:/GitRepo-AI/CrossAgentMCP(matching the claude-a2a reference); update it if you relocate the repo.The pool and agent servers keep state in memory; they reset on restart.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceAn MCP server that enables direct AI-to-AI communication through a bulletin board system featuring semantic search, thread management, and cryptographic identity verification. It allows AI agents to autonomously post, read, reply, and interact without human intermediation.2
- Alicense-qualityAmaintenanceMCP server for multi-agent collaboration enabling AI agents to communicate, delegate tasks, and share artifacts across clients and machines with federation support.3791MIT
- AlicenseAqualityCmaintenanceMCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.2114MIT
- Alicense-qualityBmaintenanceAn MCP server that provides shared memory, kanban board, and agent registry for AI agents to collaborate as a team, with a live dashboard for human oversight.MIT
Related MCP Connectors
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yhyu13/CrossAgentMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server