[ ABORT TO HUD ]
SEQ. 1
SEQ. 2
SEQ. 3
SEQ. 4
SEQ. 5

The A2A Protocol

🌐 A2A Protocol & Google ADK12 min100 BASE XP

Agent-to-Agent Communication

While MCP connects agents to tools and data, the A2A (Agent-to-Agent) protocol connects agents to other agents. Introduced by Google, A2A is an open standard for cross-vendor agent interoperability.

Why A2A?

Imagine a Claude agent that needs to book a flight. There's already a specialized travel agent (built with OpenAI). Without A2A, you'd need to build custom integration code. With A2A, the Claude agent discovers the travel agent, understands its capabilities, and delegates the task — all through a standardized protocol.

MCP vs A2A

DimensionMCPA2A
ConnectsAgent ↔ Tools/DataAgent ↔ Agent
AnalogyUSB-C (plug in peripherals)HTTP (services talk to services)
Discovery.well-known/mcp.well-known/agent-card.json
InteractionRequest/Response (tool calls)Peer-to-peer task delegation
Governed byLinux FoundationGoogle (open spec)
💡 Key Insight: MCP and A2A are complementary, not competing. An agent uses MCP to connect to databases and APIs, and A2A to delegate tasks to specialized agents. Together they form the full interoperability stack.
SYNAPSE VERIFICATION
QUERY 1 // 3
What does the A2A protocol enable?
Agents connecting to databases
Agents communicating and delegating tasks to other agents across different vendors
Agents generating images
Agents training themselves
Watch: 139x Rust Speedup
The A2A Protocol | A2A Protocol & Google ADK — AI Agents Academy