Google releases A2A protocol: opens a new era of AI agent collaboration and fully supports MCP

Google and DeepMind work together to lead new breakthroughs in the field of AI. The A2A protocol facilitates multi-agent collaboration.
Core content:
1. The A2A protocol complements the MCP and jointly promotes cross-platform intelligent agent collaboration
2. The five design principles of the A2A protocol and its working mechanism
3. Example demonstration: The application of the A2A protocol in candidate screening and future roadmap
Google released the Agent2Agent Protocol (A2A) this morning. A2A is a key step towards universal intelligent agent collaboration . It enables cross-platform and cross-vendor AI agents to truly work together, marking a leap from "single-agent intelligence" to "multi-agent system intelligence."
Link? - https://google.github.io/A2A/
The Agent-to-Agent (A2A) protocol is a standard jointly proposed by Google and DeepMind to build a communication and collaboration system between remote intelligent agents.
MCP (Multi-Agent Collaboration Protocol) is fully supported, and A2A is its supplementary protocol to address the shortcomings of MCP in practical applications.
? A2A and MCP (Anthropic) relationship
It is not competition, but complementarity . The goal is to solve the problem of lack of standards in agent calls and promote cross-platform compatibility. A2A focuses on Agent-to-Agent collaboration MCP provides context and tool standards (Model Context Protocol) The combination of the two can build a truly "end-to-end autonomous" agent ecosystem.
? Five design principles of A2A protocol
1. Embrace agent intelligence | |
2. Based on existing standards | |
3. Secure by default | |
4. Support long tasks and state management | |
5. Modality is irrelevant |
How A2A Works
A2A defines two types of roles:
Client Agent : Initiate tasks and assign collaboration Remote Agent : Receives tasks and returns results (called Artifact)
Key components:
Agent Card : A capability description file in JSON format (the "business card" of the agent) Task Object : Description of the task life cycle, including status updates, completion markers, etc. Message communication : used to transmit context, results, user instructions, etc. User Experience Negotiation : Negotiate content formats for end-user interface capabilities (video/iframe, etc.)
Example demonstration: Candidate screening
On a platform like Agentspace :
The user (HR) entrusts the main agent to find candidates for a certain position The master agent calls multiple remote talent matching agents to collect resumes After the user confirms, interviews and background checks are automatically arranged The entire process does not require manual cross-system switching, greatly improving recruitment efficiency