A2A Bridge
A2A MCP Server bridges the Model Context Protocol with Google's Agent-to-Agent protocol, enabling MCP clients like Claude to discover, register, and communicate with A2A agents through a unified interface. Developed by GongRzhe, it provides tools for agent management (registration, listing, unregistration), message sending with both synchronous and streaming responses, and task management including result retrieval and cancellation. The implementation supports multiple transport types (stdio, HTTP, SSE), includes persistent storage for agent registrations and task mappings, and handles the protocol translation between MCP's tool-based interface and A2A's JSON-RPC messaging, making it valuable for integrating existing A2A agents into MCP-compatible AI assistant workflows.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- maps-location
- Source
- PulseMCP
- Repository
- github.com/gongrzhe/a2a-mcp-server
- Author type
- human
- Updated
- 2026-08-31
Use via MCP
Resolve A2A Bridge from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.