MCP vs A2A: what is the difference?
Short answer DER
They connect different things. MCP (Model Context Protocol; maintainer: Agentic AI Foundation (Linux Foundation); licence: MIT AND Apache-2.0) is an open JSON-RPC protocol that connects an AI application to tools, resources and prompts exposed by MCP servers. A2A (Agent2Agent; maintainer: Linux Foundation (A2A Project); licence: Apache-2.0) lets agents built on different frameworks discover each other through Agent Cards and exchange tasks and messages. As of 2026-11-21, 37 of 47 platforms in AgentSidekick's records document MCP support; 1 lists A2A as an extension mechanism.
The evidence
MCP and A2A side by sideCUR
Curated from each project's specification site and repository. Stars and push dates are read from GitHub. GitHub stars measure popularity, not quality, security or fit for your use.
| Model Context Protocol (MCP) | Agent2Agent Protocol (A2A) | |
|---|---|---|
| Maintainer | Agentic AI Foundation (Linux Foundation) | Linux Foundation (A2A Project) |
| What it is | Open JSON-RPC protocol that lets AI applications connect to external tools, resources and prompts exposed by MCP servers over stdio or HTTP. Defines client/server capabilities, authorization and transport rules. | Open protocol for agents built on different frameworks to discover each other through Agent Cards and exchange tasks, messages and artifacts over HTTP, JSON-RPC or gRPC. |
| Open source | Yes | Yes |
| Licence | MIT AND Apache-2.0 | Apache-2.0 |
| Repository | modelcontextprotocol/modelcontextprotocol | a2aproject/a2a |
| GitHub stars | 9,737 | 26,617 |
| Last push | 2026-11-21 | 2026-11-20 |
| Latest version | Unknown | Unknown |
| Checked on | 2026-11-21 | 2026-11-21 |
| Notes | Created by Anthropic; donated to the Agentic AI Foundation. LICENSE file states the project is transitioning from MIT to Apache-2.0 (new contributions Apache-2.0). | Originated at Google; now hosted by the Linux Foundation. Repo google-a2a/A2A redirects here. |
What AgentSidekick's records showDER
Counts over this site's own records only; they are not adoption figures for the whole market.
| Measure | MCP | A2A |
|---|---|---|
| Platforms documenting support / listing it as an extension mechanism | 37 of 47 | 1 of 47 |
| Products of this kind in the catalogue | 69,078 MCP servers | Not tracked (A2A agents are not catalogued as a type) |
How this comparison was made. Both protocol records were researched by AgentSidekick against the specification sites and repositories listed below. Platform counts come from curated platform records. AgentSidekick publishes no adoption estimates because none could be verified.
Limit. Platform counts cover only the platforms this site tracks. A platform listing A2A as a mechanism has been recorded; how completely it implements the spec has not been checked.
Can an agent use both? Nothing in either specification excludes the other: MCP describes the agent-to-tool connection, A2A the agent-to-agent one. In our records, Amazon Bedrock AgentCore records both.
Who started each protocol? Created by Anthropic; donated to the Agentic AI Foundation (MCP). Originated at Google; now hosted by the Linux Foundation (A2A).
Which repository is more active? MCP: last push 2026-11-21. A2A: last push 2026-11-20. Push dates say a repository is maintained, not how widely the protocol is used.
Related
Sources
Pages the records behind this answer were taken from. Counts and rankings are computed by the site from these records.
- Model Context Protocol (MCP): modelcontextprotocol.io (external)checked
- Model Context Protocol (MCP): modelcontextprotocol.io (external)checked
- Model Context Protocol (MCP): github.com (external)checked
- Agent2Agent Protocol (A2A): a2a-protocol.org (external)checked
- Agent2Agent Protocol (A2A): a2a-protocol.org (external)checked
- Agent2Agent Protocol (A2A): github.com (external)checked
How claims are labelled and ranked: claim kinds, ranking rules, compatibility statuses. Spotted an error? See corrections.