A
licenseNot graded
qualityC
maintenanceEnables AI agents to communicate with business agents across company boundaries using Google's A2A protocol, with tools for discovery, messaging, and connection management.
MIT
a2a-mcp-connector
Related Servers
Alternatives to a2a-mcp-connector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to connect and interact with A2A Protocol agents, allowing discovery of agent capabilities, sending messages to remote agents, managing multi-turn conversations, and viewing artifacts returned by agents.16Apache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects MCP-powered AI agents to the decentralized Agent Network Protocol (ANP) for DID-based identity, agent discovery, and secure agent-to-agent communication.MIT
- AlicenseAqualityDmaintenanceEnables LLMs to communicate with Agent-to-Agent (A2A) protocol compliant agents, providing tools for sending messages, managing tasks, and retrieving agent information.49 npmMIT
- AlicenseBqualityDmaintenanceConnects any MCP-compatible AI client to Letta.ai's stateful agents for agent conversations, memory management, and tool orchestration.1812MIT
- AlicenseAqualityCmaintenanceDiscover and connect your agents with other agents via A2A protocol. Share resources for free or fee.6MIT
TDQS
A4.5/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a distinct responsibility: validate checks the Agent Card, connect establishes the session, send/wait_turn handle messaging, status reports state, and leave tears down. No functional overlap or ambiguity exists.
Naming Consistency4/5
All tools use the a2a_ prefix and mostly use verb-led names like connect, send, leave, and validate. The sole exception is a2a_status, which is a noun rather than an imperative verb, but it remains clear and aligned with the overall pattern.
Tool Count5/5
Six tools is appropriate for a focused A2A connector: validation, connection, turn-based messaging, status polling, and disconnection. The toolset is lean without missing necessary lifecycle operations.
Completeness5/5
The toolset covers the full A2A session lifecycle: validate, connect, send, wait for turn, check status, and leave. No essential operation for interacting with a remote agent over this protocol appears to be missing.
Maintenance
ActivityMaintained
ResponsivenessNo issues