What is the enterprise AI agent protocol coalition?

In early August 2026, Google, Microsoft, Salesforce, Snowflake and ServiceNow reportedly teamed up on a shared enterprise AI agent protocol — a standard for agents to interoperate across their platforms. It's widely read as a move to blunt Anthropic's Model Context Protocol (MCP), which became the de facto agent-tool standard in 2025-2026.

How is this different from MCP?

MCP (Anthropic, open-sourced 2024) standardizes how a single agent connects to tools and data. The enterprise coalition's protocol targets agent-to-agent interoperability and governance across large vendor platforms — control-tower features like observability, permissions, and cross-vendor orchestration that big enterprises want and that MCP alone doesn't fully cover.

Does this replace MCP?

Not directly. MCP solves the tool-connection layer and has broad adoption; the coalition protocol targets enterprise orchestration and governance across vendors. The likely 2026 outcome is coexistence — MCP for tool access, an enterprise layer on top — but the politics of a Google/Microsoft-led standard versus Anthropic's is the story to watch.

Quick Answer

Enterprise Agent Protocol vs MCP: The 2026 Split

Published: August 6, 2026

The Short Answer

In early August 2026, reports say Google, Microsoft, Salesforce, Snowflake and ServiceNow are teaming on a shared enterprise AI agent protocol — explicitly framed as a move to blunt Anthropic’s Model Context Protocol (MCP). It signals the agent-interop layer is now a standards battleground between hyperscalers and Anthropic.

The Two Layers

	MCP (Anthropic)	Enterprise coalition protocol
Backers	Anthropic (open standard, 2024)	Google, Microsoft, Salesforce, Snowflake, ServiceNow
Focus	Agent ↔ tool/data connection	Agent-to-agent interop + governance
Adoption	De facto standard 2025-2026	Newly announced, forming
Strength	Simple, broad tool ecosystem	Enterprise control, cross-vendor orchestration

Why the Big Vendors Are Moving

MCP won the tool-connection layer fast. But large enterprises want more: a control tower — observability across agents, permissions and audit, and orchestration that spans Agentforce, Copilot, Snowflake Cortex, and Bedrock in one view. A standard owned by the platform incumbents gives them that governance layer (and keeps the standard from being defined solely by Anthropic).

What It Means

Coexistence, not replacement: MCP handles tool access; the enterprise layer sits on top for cross-vendor orchestration and governance. Expect both.
Standards politics: This is as much about who controls the agent stack as about technology. Anthropic set the pace with MCP; the incumbents don’t want a rival defining the enterprise agent layer.
Buyer impact: If you’re building agent infrastructure, don’t bet everything on one protocol yet. Design for MCP tool access now, but track the coalition spec before committing to a governance layer.

The Watch-Out

Vendor coalitions have a poor track record of shipping clean, adopted standards fast — competing interests slow them down. MCP’s advantage is that it already works and is deployed. The coalition’s advantage is enterprise reach. Whether it becomes real infrastructure or a press release depends on shipped specs, not the announcement.

Sources

AI Weekly — coalition to blunt Anthropic’s MCP: aiweekly.co
Shashi.co — ServiceNow / Microsoft / Boomi control tower: shashi.co
Anthropic — Model Context Protocol: anthropic.com/news