Agent protocols: A2A, MCP and the two ACPs

How do A2A, MCP and ACP compare at a glance?

Table. A2A, MCP and the two ACPs at a glance.
A2A (Agent2Agent)MCP (Model Context Protocol)ACP: Agent Communication Protocol (IBM / BeeAI)ACP: Agent Client Protocol
ConnectsAgent to agentAgent (host/client) to tools and data (server)Agent to agentCode editor to coding agent
OriginGoogle, April 2025Originally created by Anthropic; now an open standardIBM, March 2025See agentclientprotocol.com
GovernanceLinux Foundation A2A project (launched 23 June 2025); joined the Agentic AI Foundation (AAIF), announced 27 August 2026AAIF project (founding project of the Linux Foundation's Agentic AI Foundation)Donated to LF AI & Data; merging into A2A (announced 29 August 2025)Project site
Current versionv1.0.1 (28 May 2026) is the latest release; v1.0.0 on 12 March 2026Specification revision 2026-07-28Development stopped; migrate to A2ALocal agents over stdio; remote support in progress
TransportJSON-RPC binding; Agent Cards for discoveryJSON-RPC 2.0Not applicable (merged)JSON-RPC over stdio (remote HTTP/WebSocket in progress)
Enterprise relevanceHigh: cross-vendor agent callsHigh: tool and data accessHistorical; use A2ADeveloper tooling: editors and coding agents (BAND lists ACP for coding agents via BAND for desktop)

What is A2A (Agent2Agent)?

A2A is an open protocol that lets agents built on different frameworks communicate. Agents interact "without needing to share internal memory, tools, or proprietary logic", and publish Agent Cards so others can discover them. Google announced A2A in April 2025; the Linux Foundation launched the A2A project on 23 June 2025 with more than 100 supporting companies and founding members Google Cloud, AWS, Cisco, Salesforce, SAP, Microsoft and ServiceNow. The technical steering committee includes AWS, Cisco, Google, IBM Research, Microsoft, Salesforce, SAP and ServiceNow. Version 1.0.0, released 12 March 2026, was a major release with breaking changes, including OAuth 2.0 modernization and a specification refactor. Version 1.0.1, released 28 May 2026, is the latest release and prefers the application/a2a+json media type. A2A joined the Agentic AI Foundation (AAIF), announced on a2a-protocol.org on 27 August 2026. Version 0.3.0 (30 July 2025) added mTLS and signed Agent Cards; several products still target v0.3.

Buyer note: ask vendors which A2A version they support. Microsoft Foundry supports v1.0 (GA) and v0.3 (preview); Gemini Enterprise registration requires a v0.3-compatible agent, with v1.0.0+ via compatibility packages.

What is MCP (Model Context Protocol)?

MCP was originally created by Anthropic and is now an AAIF project. It is an open standard for connecting AI applications to external systems, described by its documentation as "like a USB-C port for AI applications". It uses JSON-RPC 2.0 between hosts, clients and servers. Servers expose resources, prompts and tools; clients can support elicitation. Extensions include Tasks for long-running work, Skills over MCP and MCP Apps for inline interfaces. The latest specification revision is dated 28 July 2026. MCP is a founding project of the Linux Foundation's Agentic AI Foundation (AAIF), alongside goose and AGENTS.md; AAIF also hosts agentgateway and lists A2A among its projects.

Buyer note: MCP is about tools, not agent collaboration. An agent can be exposed as an MCP tool, but that makes it a function another agent calls, not a peer.

What are the two ACPs?

Agent Communication Protocol (IBM / BeeAI). Launched by IBM in March 2025 and contributed to the Linux Foundation's LF AI & Data. On 29 August 2025, LF AI & Data announced that ACP was joining forces with A2A: the ACP team stopped active development, IBM's Kate Blair joined the A2A technical steering committee, and BeeAI moved to A2A through adapters. If an RFP response cites this ACP, ask about the A2A migration path.

Agent Client Protocol. A different standard that connects code editors and IDEs to coding agents, often described as an "LSP for agents". It runs JSON-RPC over stdio for local agents, reuses MCP JSON types, and has remote transport over HTTP or WebSocket in progress. It matters for developer tooling (for example, running coding agents inside an editor) rather than for enterprise agent-to-agent traffic.

How to tell them apart: "ACP" is used for both protocols, so check which one a vendor means. The Agent Communication Protocol (IBM / BeeAI) covers agent-to-agent messaging and is now folded into A2A. The Agent Client Protocol covers editors and coding agents and is in active development. BAND lists the Agent Client Protocol on its integrations page for coding agents, used with BAND for desktop.

Where do protocols stop?

Protocols define how a call is made. They do not define:

These are coordination functions. BAND supports MCP, A2A and the Agent Client Protocol, and provides these coordination functions in its collaboration layer: @mention routing, shared memories, room activity timelines, cross-account agent discovery, and people approving, redirecting or overriding in place.

Which vendors support A2A and MCP?

Table. Vendor protocol support; BAND updated November 2026, other protocol research September 2026.
VendorA2AMCPNotes
BANDYesYesAlso lists ACP (Agent Client Protocol) for coding agents via BAND for desktop; A2A SDK adapter and gateway; ACP server and client adapter; MCP
Solace Agent MeshYesYesEvent-broker transport
MuleSoft Agent FabricYes (connectors)Yes (MCP Bridge)APIs to MCP tools
Kong Agent GatewayYes (proxy)Yes (MCP Registry)Audit log per A2A RPC
Solo.io agentgatewayYes (federation)Yes (native)Apache 2.0, AAIF hosted
ServiceNow AI Control TowerYes (Action Fabric)Yes (client)Inventories MCP servers
IBM watsonx OrchestrateYesYesDiscovers agents on other platforms
Microsoft Foundry Agent ServiceYes (v1.0 GA)Yesv0.3 in preview
Amazon Bedrock AgentCoreYesYesRuntime also supports HTTP and AG-UI
Google Gemini EnterprisePreviewYes (data sources)Requires self-hosted A2A agent
Salesforce AgentforceNot confirmedYes (verified partners)Salesforce is on the A2A TSC

Source: a2a-protocol.org/latest , github.com/a2aproject/A2A/releases , linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents , modelcontextprotocol.io/specification/latest , modelcontextprotocol.io/docs/getting-started/intro , aaif.io/projects , lfaidata.foundation/communityblog/2025/08/29/acp-joins-forces-with-a2a-under-the-linux-foundations-lf-ai-data , agentclientprotocol.com , band.ai/integrations?utm_source=distributedaiagents.com&utm_medium=referral · Reviewed Sep 2026

What do buyers ask about agent protocols?

What is the difference between A2A and MCP?

MCP connects an agent to tools and data. A2A connects an agent to other agents. They are complementary; most enterprise architectures need both.

Does BAND support A2A, ACP and MCP?

Yes. BAND supports A2A, ACP and MCP. Its SDK implements an A2A adapter and gateway; ACP has server and client adapters. Shared rooms provide @mention routing, memories, activity timelines and human participation.

Is ACP a competitor to A2A?

The IBM Agent Communication Protocol merged into A2A in 2025. The Agent Client Protocol solves a different problem, connecting editors to coding agents.

Which A2A version should I require?

Ask for v1.0 support, since v1.0.0 (March 2026) introduced breaking changes. Accept v0.3 compatibility where a platform still requires it, such as Gemini Enterprise registration.

Which detailed infrastructure guides should you read?