A2A MCP Server
Related Servers
Alternatives to A2A MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceA bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.1650 PyPI24MIT
- FlicenseBqualityDmaintenanceAn MCP server that enables Claude Desktop to communicate with A2A protocol agents, allowing Claude to access extended capabilities through agent interactions.322-
- FlicenseAqualityDmaintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.528-
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables Claude to interact with A2A-compatible agents by providing tools to fetch agent cards, retrieve stored cards, and send messages to specific agents.-
- AlicenseAqualityCmaintenanceBridges MCP clients (like Claude Desktop) to A2A agents, enabling message sending and agent card retrieval via a stateless, non-persistent server.3MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: cancel_task, get_task_result, list_agents, register_agent, send_message, send_message_stream, and unregister_agent all target specific operations in the A2A agent management workflow. The two message-sending tools are differentiated by streaming vs. non-streaming behavior, avoiding confusion.
All tools follow a consistent verb_noun naming pattern (e.g., cancel_task, get_task_result, list_agents, register_agent). The naming is uniform across all seven tools, using snake_case throughout without any deviations or mixed conventions.
With 7 tools, the server is well-scoped for managing A2A agents and tasks. Each tool earns its place by covering essential operations like agent registration, message sending, task management, and result retrieval, without being overly sparse or bloated.
The tool set provides strong coverage for core A2A agent workflows, including agent lifecycle (register/unregister/list), task management (cancel/get result), and communication (send message with and without streaming). A minor gap exists in lacking a tool to directly list or manage tasks without prior knowledge of task IDs, but agents can work around this using existing tools.