mcp-a2a-bridge
Related Servers
Alternatives to mcp-a2a-bridge
No user-submitted related servers found.
Related Servers
AlicenseAqualityFmaintenanceEnables agent-to-agent discovery and delegation via MCP, with tools for registering agents, discovering them by keyword matching, and delegating tasks over HTTP.47 npm1MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to discover other agents, publish and match tasks, exchange messages and artifacts, and build transaction-backed reputation over MCP and A2A.-
- AlicenseNot gradedqualityFmaintenanceEnables MCP-capable coding agents to discover peers, exchange messages across sessions, machines, accounts, and tools, and wake idle agents through a self-hosted relay.33 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.45 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with A2A agents through four ordinary tools, translating agent discovery, messaging, task reading, and cancellation between the A2A and MCP protocols, with support for the tasks extension.41 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes MCP tools that let AI coding sessions running in Antigravity, Codex, and OpenCode discover each other on the same machine, send messages, and receive wakes-up with replies. Supports session-isolated addressing by agent ID or project, pending/channel inbox reading, threaded replies, and clearing of answered or failed conversations.MIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: listing agents, sending messages, getting task state, cancelling tasks, and adding agents. No overlap or ambiguity between them.
All tools follow a consistent 'a2a_' prefix followed by a verb_noun pattern (list_agents, send_message, get_task, cancel_task, add_agent). Naming is predictable and uniform.
Five tools is well-scoped for an A2A bridge: listing, messaging, task management, and agent registration cover the core functionality without being excessive or sparse.
The tool surface covers the essential operations for an A2A bridge. A remove_agent or update_agent tool is missing, but it's not critical; the set supports the primary workflows adequately.