
A2a Bridge
- 1 repo stars
- Updated April 24, 2026
- mdfifty50-boop/a2a-bridge-mcp
io.github.mdfifty50-boop/a2a-bridge is an MCP server that bridges agent-to-agent communication in multi-agent setups.
About
io.github.mdfifty50-boop/a2a-bridge is a Model Context Protocol server that acts as a communication bridge between agents in multi-agent systems. developers experimenting with planner–executor splits, reviewer sidecars, or domain-specific subagents can register this stdio MCP package so tools expose agent-to-agent messaging patterns instead of cramming every role into one chat. The server ships via npm as a2a-bridge-mcp at version 0.1.1 with local stdio transport, which matches how most Claude Code and Cursor users run auxiliary MCP processes on the same machine. It sits in the build phase under agent-tooling because its value appears when you architect how multiple LLM agents collaborate during implementation—not when you are validating market fit or tuning production monitors. Expect intermediate complexity: you need Node, MCP config literacy, and a clear protocol for which agent speaks to which peer. It complements orchestration skills and custom prompts but does not replace a full message bus or enterprise A2A standard by itself.
- npm package a2a-bridge-mcp v0.1.1 with stdio MCP transport for local agent hosts
- Agent-to-agent communication bridge aimed at multi-agent system topologies
- stdio transport fits Claude Code and local MCP runners without hosting a remote gateway
- Open-source repo at github.com/mdfifty50-boop/a2a-bridge-mcp for inspection and forks
- Foundation layer for delegating subtasks between specialized agents instead of one monolithic prompt
A2a Bridge by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add a2a-bridge-mcp -- npx -y a2a-bridge-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | a2a-bridge-mcp |
| Transport | STDIO |
| Auth | None |
| Last updated | April 24, 2026 |
| Repository | mdfifty50-boop/a2a-bridge-mcp ↗ |
What it does
Let separate agents exchange messages and coordinate handoffs in a multi-agent coding or ops setup via MCP.
Who is it for?
Best when you're prototyping multi-agent pipelines locally with npm-based MCP and stdio transport.
Skip if: Simple single-agent apps that do not need inter-agent messaging or production-grade enterprise agent buses.
What you get
You install a stdio MCP bridge so agents can coordinate through defined tools rather than manual copy-paste between terminal sessions.
- Running stdio MCP bridge process in agent config
- Tool surface for agent-to-agent coordination patterns
- Clearer separation of specialized agents in local workflows
By the numbers
- Published version 0.1.3 is costcenter sibling; a2a-bridge version 0.1.1
- npm identifier a2a-bridge-mcp with stdio transport
- Repository https://github.com/mdfifty50-boop/a2a-bridge-mcp
README.md
a2a-bridge-mcp
MCP server for agent-to-agent communication -- capability discovery, task delegation, and result aggregation across MCP agents.
MCP connects agents to tools, but not to each other. This server adds a standardized agent-to-agent layer within the MCP protocol -- register agents, discover capabilities, delegate tasks, and broadcast work to multiple agents. Inspired by Google's A2A protocol.
Install
npx a2a-bridge-mcp
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"a2a-bridge": {
"command": "npx",
"args": ["a2a-bridge-mcp"]
}
}
}
From source
git clone https://github.com/mdfifty50-boop/a2a-bridge-mcp.git
cd a2a-bridge-mcp
npm install
node src/index.js
Tools
register_agent
Register an agent with capabilities for discovery by other agents.
| Param | Type | Default | Description |
|---|---|---|---|
agent_id |
string | required | Unique agent identifier |
capabilities |
string[] | required | Capability strings (e.g. ["code-review", "summarization"]) |
description |
string | "" |
Human-readable description |
input_schema |
object | {} |
JSON schema for accepted input |
output_schema |
object | {} |
JSON schema for produced output |
endpoint |
string | "" |
Optional endpoint or transport hint |
discover_agents
Find agents matching a capability need with fuzzy text similarity scoring.
| Param | Type | Default | Description |
|---|---|---|---|
capability_needed |
string | required | Capability to search for |
min_score |
number | 0.3 | Minimum similarity score (0-1) |
Returns scored matches sorted by relevance.
delegate_task
Delegate a task to a specific registered agent. Creates a tracked task with status lifecycle.
| Param | Type | Default | Description |
|---|---|---|---|
from_agent |
string | required | Delegating agent ID |
to_agent |
string | required | Target agent ID |
task_description |
string | required | What the target should do |
input_data |
object | {} |
Input data for the task |
timeout_ms |
number | 30000 | Timeout in milliseconds |
Returns a task_id for tracking.
get_task_result
Get status and result of a delegated task. Also used by executing agents to submit results.
| Param | Type | Description |
|---|---|---|
task_id |
string | Task ID from delegate_task or broadcast_task |
submit_result |
object | (Optional) Submit completion result |
submit_error |
string | (Optional) Submit failure error |
Status lifecycle: pending -> running -> completed / failed.
broadcast_task
Send a task to ALL agents matching a capability. Creates individual tracked tasks for each match.
| Param | Type | Default | Description |
|---|---|---|---|
from_agent |
string | required | Broadcasting agent ID |
capability_needed |
string | required | Capability to match |
task_description |
string | required | What matched agents should do |
input_data |
object | {} |
Input data |
min_score |
number | 0.3 | Minimum match score |
timeout_ms |
number | 30000 | Timeout per agent |
Returns list of task IDs for aggregation via get_task_result.
get_agent_card
Get an agent's full capability card with schemas, stats, and task history.
| Param | Type | Description |
|---|---|---|
agent_id |
string | Agent identifier |
Returns capabilities, input/output schemas, success rate, and task counts. Inspired by Google A2A agent cards.
list_agents
List all registered agents, optionally filtered by capability.
| Param | Type | Default | Description |
|---|---|---|---|
filter |
string | "" |
Capability keyword to filter by (empty = all) |
Resources
| URI | Description |
|---|---|
a2a://agents |
All registered agents with capabilities and stats |
Usage Pattern
1. register_agent -- each agent registers at startup
2. discover_agents -- find who can handle a task
3. delegate_task -- send work to a specific agent
OR broadcast_task -- send work to all matching agents
4. get_task_result -- poll for completion or submit results
5. get_agent_card -- inspect an agent's full profile
6. list_agents -- overview of the agent network
Multi-agent workflow example
Agent A (orchestrator):
1. register_agent(agent_id="orchestrator", capabilities=["planning", "coordination"])
2. discover_agents(capability_needed="code review")
-> finds Agent B (score: 0.95)
3. delegate_task(from="orchestrator", to="agent-b", task="Review PR #42")
-> task_id: "task_1234"
4. get_task_result(task_id="task_1234")
-> status: "completed", result: { approved: true, comments: [...] }
Agent B (worker):
1. register_agent(agent_id="agent-b", capabilities=["code-review", "linting"])
2. (receives task via external notification or polling)
3. get_task_result(task_id="task_1234", submit_result={ approved: true })
License
MIT
Recommended MCP Servers
How it compares
Local MCP stdio bridge for agent messaging, not a hosted todo service or billing dashboard.
FAQ
Who is io.github.mdfifty50-boop/a2a-bridge for?
Developers assembling multi-agent systems in Claude Code or similar hosts who need MCP-accessible agent-to-agent communication.
When should I use io.github.mdfifty50-boop/a2a-bridge?
Use it during build when you split work across multiple agents and need a bridge layer exposed as MCP tools over stdio.
How do I add io.github.mdfifty50-boop/a2a-bridge to my agent?
Install the npm package a2a-bridge-mcp, add a stdio MCP server entry pointing at that binary in your client config, and restart the MCP connection.