---
title: "What is the A2A protocol? Agent2Agent explained"
description: "The A2A (Agent2Agent) protocol is an open standard that lets AI agents from different vendors find each other and delegate tasks. See how it compares to MCP."
type: "glossary-term"
canonical_url: "https://theaiengineering.com/glossary/a2a-protocol"
markdown_url: "https://theaiengineering.com/glossary/a2a-protocol.md"
topic: "Model Context Protocol"
author: "The AI Engineering Editors"
publisher: "The AI Engineering"
updated: "2026-11-06"
keywords: ["A2A protocol","Agent2Agent protocol","A2A","agent-to-agent protocol"]
citation: "The AI Engineering Editors. \"What is the A2A protocol? Agent2Agent explained.\" The AI Engineering, updated Nov 06, 2026. https://theaiengineering.com/glossary/a2a-protocol"
---

# What is the A2A protocol? Agent2Agent explained

Also called Agent2Agent protocol, A2A, agent-to-agent protocol.

> **Definition of A2A protocol:** The A2A (Agent2Agent) protocol is an open standard, introduced by Google in April 2025, that lets AI agents built on different frameworks discover each other, exchange messages, and delegate tasks.

The A2A (Agent2Agent) protocol is an open standard for communication between [AI agents](https://theaiengineering.com/glossary/ai-agent). Google [announced A2A](https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/) on April 9, 2025, with support from more than 50 technology partners, and later donated it to the Linux Foundation; the project has since joined the Agentic AI Foundation. A2A lets an agent built with one framework or vendor hand work to an agent built with another. A2A treats the remote agent as a black box: the client sees its declared skills, not its internal logic, memory, or tools.

## How the A2A protocol works

The A2A protocol works by having a client agent send tasks to a remote agent that advertises its skills. The core objects in the [A2A specification](https://a2a-protocol.org/latest/specification/) are:

- **[Agent Card](https://theaiengineering.com/glossary/agent-card)**: a JSON document, published at `/.well-known/agent-card.json` on the agent's domain, that lists the agent's identity, endpoint, skills, supported features, and authentication requirements.
- **Task**: the unit of work, with a server-generated ID and a lifecycle of states including submitted, working, input-required, completed, failed, and canceled.
- **Message and Part**: a message is one turn of communication, made of parts that carry text, file references, or structured data.
- **Artifact**: an output the remote agent produces for a task.

Version 1.0 of the specification defines protocol bindings for [JSON-RPC 2.0](https://theaiengineering.com/glossary/json-rpc), gRPC, and HTTP+JSON. Streaming updates use Server-Sent Events, and long-running tasks can report progress through push notifications to a client-registered webhook.

## A2A vs MCP

A2A and MCP are complementary: [MCP](https://theaiengineering.com/glossary/model-context-protocol) connects an agent to tools and data, and A2A connects an agent to other agents. The A2A project describes the two the same way and states that A2A is not a replacement for MCP.

| | MCP | A2A |
|---|---|---|
| Connects | Agent to tools and data sources | Agent to agent |
| Remote side | A server exposing tools, resources, and prompts | An opaque agent exposing skills |
| Unit of work | A tool call | A task with a lifecycle |
| Discovery | `tools/list` and other list methods | Agent Card |
| Origin | Anthropic, November 2024 | Google, April 2025 |

A [multi-agent system](https://theaiengineering.com/glossary/multi-agent-system) can use both: each agent reaches its own tools through MCP and delegates to specialist agents through A2A. [A2A vs MCP](https://theaiengineering.com/articles/a2a-vs-mcp) compares the protocols in depth, and the [MCP topic hub](https://theaiengineering.com/topics/mcp) covers the wider protocol landscape.

## Related terms

- [Model Context Protocol (MCP)](https://theaiengineering.com/glossary/model-context-protocol): Model Context Protocol (MCP) is an open protocol, introduced by Anthropic in November 2024, that standardizes how AI applications connect to external tools, data sources, and prompts through MCP servers.
- [Multi-agent system](https://theaiengineering.com/glossary/multi-agent-system): A multi-agent system is an AI architecture in which several language-model agents, each with its own prompt, tools, and context, work on parts of a task and pass results to one another.
- [AI agent](https://theaiengineering.com/glossary/ai-agent): An AI agent is a software system in which a large language model runs in a loop, calling tools, reading their results, and repeating until the task is complete or a stop condition is reached.
- [Agentic AI](https://theaiengineering.com/glossary/agentic-ai): Agentic AI is the class of AI systems that pursue a goal through multiple steps, using a language model to plan, call tools, and act on the results with limited human input.
- [Agent Card](https://theaiengineering.com/glossary/agent-card): An Agent Card is a JSON document that an A2A server publishes, usually at /.well-known/agent-card.json, describing the agent's identity, endpoints, capabilities, skills, and authentication requirements.
- [JSON-RPC](https://theaiengineering.com/glossary/json-rpc): JSON-RPC is a lightweight, transport-agnostic remote procedure call protocol that encodes method calls, results, and errors as JSON objects; version 2.0 is the message format of MCP and A2A.

## Guides that cover a2a protocol

- [A2A protocol vs MCP: differences and when to use each](https://theaiengineering.com/articles/a2a-vs-mcp): A2A protocol vs MCP: A2A connects AI agents to other agents, and MCP connects an agent to tools and data. Compare agent cards, tasks, transports, and security.
- [What is the Model Context Protocol (MCP)? How it works](https://theaiengineering.com/articles/what-is-model-context-protocol): The Model Context Protocol (MCP) is an open standard for connecting AI apps to tools and data. Learn its architecture, transports, tool calls, and security.
- [Bifrost vs LiteLLM: architecture, features, and performance compared](https://theaiengineering.com/articles/bifrost-vs-litellm): Bifrost vs LiteLLM compared: a Go single binary against a Python proxy, with deployment, routing, virtual keys, caching, MCP, benchmarks, and migration.
- [AI agent frameworks compared: LangGraph, CrewAI, ADK, and more](https://theaiengineering.com/articles/ai-agent-frameworks): An AI agent frameworks comparison of LangGraph, LangChain, CrewAI, the OpenAI, Claude, and Google SDKs, Pydantic AI, Mastra, and more, by language and license.
- [What is an AI gateway? How it works and when you need one](https://theaiengineering.com/articles/what-is-an-ai-gateway): An AI gateway is a proxy between your apps and model providers. Learn how it works, its core features, AI gateway vs API gateway, and open source options.
- [What are AI agents? How agents work and when to use one](https://theaiengineering.com/articles/what-are-ai-agents): AI agents are LLM systems that call tools in a loop until a task is done. Learn how the loop works, agents vs agentic AI, examples, failure modes, and limits.

Part of the [Model Context Protocol](https://theaiengineering.com/topics/mcp) topic hub.

## Cite this definition

The AI Engineering Editors. "What is the A2A protocol? Agent2Agent explained." The AI Engineering, updated Nov 06, 2026. https://theaiengineering.com/glossary/a2a-protocol

- Title: What is the A2A protocol? Agent2Agent explained
- Author: The AI Engineering Editors
- Publisher: The AI Engineering
- Updated: 2026-11-06
- URL: https://theaiengineering.com/glossary/a2a-protocol
- Markdown: https://theaiengineering.com/glossary/a2a-protocol.md
