Agent2Agent (A2A) Protocol¶
In a world where agents are built using diverse frameworks and by different vendors, A2A provides a common language, breaking down silos and fostering interoperability.
Build with
ADK (or any framework),
equip with MCP (or any tool),
and communicate with
A2A,
to remote agents, local agents, and humans.
-
A2A Announcements
Ramp up quickly
Announcing the A2A Protocol (Apr) our initial blog
Agents are not tools (Jun) our TL thought piece
Google Cloud donates A2A to Linux Foundation (Jun) covered by Forbes
Dive deep with end to end examples
-
Video Intro in <8 min
Why A2A Matters¶
-
Interoperability
Connect agents built on different platforms (LangGraph, CrewAI, Semantic Kernel, custom solutions) to create powerful, composite AI systems.
-
Complex Workflows
Enable agents to delegate sub-tasks, exchange information, and coordinate actions to solve complex problems that a single agent cannot.
-
Secure & Opaque
Agents interact without needing to share internal memory, tools, or proprietary logic, ensuring security and preserving intellectual property.
A2A and MCP: Complementary Protocols¶
A2A and the Model Context Protocol (MCP) are complementary standards for building robust agentic applications:
- MCP (Model Context Protocol): Connects agents to tools, APIs, and resources with structured inputs/outputs. Think of it as the way agents access their capabilities.
- A2A (Agent2Agent Protocol): Facilitates dynamic, multimodal communication between different agents as peers. It's how agents collaborate, delegate, and manage shared tasks.
Get Started with A2A¶
-
Read the Introduction
Understand the core ideas behind A2A.
-
Dive into the Specification
Explore the detailed technical definition of the A2A protocol.
-
Follow the Tutorials
Build your first A2A-compliant agent with our step-by-step Python quickstart.
-
Explore Code Samples
See A2A in action with sample clients, servers, and agent framework integrations.