What is ACP and how does it position relative to MCP and A2A in the 2026 agent protocol landscape?
Describe ACP (Agent Communication Protocol) and explain how it relates to MCP and A2A in the agent protocol ecosystem as of 2026. How is each protocol governed?
Three protocols, three boundaries: MCP wires agents to tools, A2A delegates tasks across orgs, ACP is REST-based general agent messaging. Complementary layers, no single governance body.
Think of a busy office. MCP is the standard wall socket every gadget plugs into to get power and data; it connects one worker to all their tools. A2A is the courier service that hands a sealed work order to another company's office and waits for the finished result. ACP is the open inbox where any worker can drop a rich message, attach files, and have a back and forth conversation, even if the two sides never agreed on a format in advance. None of these replaces the others. You still need sockets for your tools, couriers for outside jobs, and an inbox for general chatter. The catch in 2026: each system was built by a different landlord, so there is no single building manager making them all work together perfectly yet.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: map all three protocols to their boundaries, give origin and date for each, explain why MCP won the tool layer, then cover the A2A vs ACP overlap and the no single foundation governance reality.
| Dimension | MCP | A2A | ACP |
|---|---|---|---|
| Boundary | Agent to tools and data | Agent to agent, cross-org delegation | Agent to agent, general messaging |
| Origin | Anthropic, Nov 2024 | Google, April 2025 | IBM Research, BeeAI |
| Core unit | Tools, resources, prompts | Capability card, task lifecycle | Rich multi-turn messages |
| Transport style | JSON-RPC over stdio or HTTP | HTTP-based task exchange | REST-based messaging |
| Governance | Open spec under Anthropic | Linux Foundation | IBM and community |
| 2026 status | Dominant at tool layer | Leading cross-org delegation | Exploratory, overlaps A2A |
Real products, models, and research that use this idea.
- Anthropic maintains MCP as an open spec with reference servers; Cursor and Zed adopted it so one server runs across hosts.
- Google introduced A2A in April 2025 with launch partners, then donated it to the Linux Foundation for neutral governance.
- IBM Research's BeeAI project drives ACP as a REST-based agent-messaging standard, distinct from A2A's task-delegation framing.
- A modern agent stack in 2026 can use MCP for its own tools and A2A or ACP to coordinate with external agents simultaneously.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy did MCP win the tool-connectivity layer when other tool standards existed?
QA2A and ACP both target agent to agent communication. Where do they overlap and where might they converge?
QIf there is no unified governance body, how does interoperability actually emerge across these protocols?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Framing the three as competitors fighting for one slot. They sit at different boundaries: tool connectivity, cross-org delegation, and general agent messaging.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.