TITLE: Five Tech Giants Unite Against Anthropic's AI Agent Standard DATE: 2026-07-14 COMPANY: Google, Microsoft, Salesforce, Snowflake, ServiceNow TOPIC: Agent Systems SUMMARY: Google, Microsoft, Salesforce, Snowflake, and ServiceNow agreed on 13 July 2026 to back a shared standard for connecting AI agents to business software, positioning the alliance as a direct alternative to Anthropic's Model Context Protocol. MCP has been the de facto standard for AI agent integration for roughly 18 months, and the five companies backing its rival collectively own the software platforms where the majority of enterprise business data resides. The new standard is built on Google's Agent-to-Agent (A2A) protocol and is designed to let agents from different vendors collaborate across Salesforce, ServiceNow, Snowflake, and Azure environments without requiring Anthropic's protocol as the connector. WHAT CHANGED: On 13 July 2026, Google, Microsoft, Salesforce, Snowflake, and ServiceNow announced they would jointly back a shared standard for connecting AI agents to enterprise business software. The standard is built on Google's existing A2A protocol, which the company developed as a specification for orchestrating multiple AI agents from different vendors on a single task. The backdrop is Anthropic's Model Context Protocol. Released in late 2024, MCP became the dominant integration layer for AI agents within roughly 18 months, adopted as a standard connection method across a wide range of AI tools and developer frameworks. Its growth came primarily from the bottom up: developers adopted it because it was open, well-documented, and supported by Anthropic's Claude, which had become a widely deployed enterprise AI. The five vendors in this new alliance make the bulk of the software where enterprise data lives. Salesforce manages customer relationships and sales pipelines. ServiceNow manages IT workflows and operational processes. Snowflake holds structured data that powers reporting and analytics. Microsoft runs Azure infrastructure and the Office 365 productivity layer. Google operates Cloud infrastructure and Workspace. Their concern is that Anthropic's protocol, embedded in their platforms, gives a competitor structural control over how AI agents connect to the tools these five companies sell and maintain. A2A is positioned as the standard for orchestration between agents from different vendors. Its practical implication is interoperability without forcing any single AI provider to be the connectivity layer. A Salesforce Agentforce agent could hand a task to a Google Vertex AI agent, which could retrieve data from a ServiceNow agent, all through A2A, without requiring Anthropic's MCP as the connector. WHY IT MATTERS: The connectivity layer is becoming as important as the model itself. The AI model your business uses will continue to commoditise. The integration layer, the protocol through which agents access your CRM, your databases, and your workflows, is becoming the more durable competitive advantage. Whoever controls that standard shapes the AI agent market for years. Enterprise platforms are not neutral in this competition. If you use Salesforce, ServiceNow, or Snowflake, the vendors you pay for have now formally taken a position. Their native agent capabilities will be optimised for A2A. That does not mean MCP will stop working inside those platforms, but it does mean future native features, deeper integrations, and certified agent workflows will be built with A2A as the priority. Anthropic's MCP has momentum that will not disappear overnight. MCP has 18 months of ecosystem adoption, an enormous developer community, and is embedded in Claude, ChatGPT plugins, and most of the major AI development frameworks. Displacing it requires the A2A alliance to ship high-quality tooling, documentation, and platform integrations at pace. Standards wars in enterprise software typically take two to four years to resolve. The Linux Foundation parallel signals that the two camps are not irreconcilable. All the major players are simultaneously working on open shared standards through the Linux Foundation. The A2A alliance may function as a vendor coalition applying competitive pressure rather than an attempt to fragment the market permanently. The end state could be a unified standard that incorporates elements of both approaches. This is a risk signal for bespoke integration work. Any organisation that has spent engineering budget building custom AI agent connectors on either MCP or A2A is now sitting on a potential technical liability. The protocol layer is in active contest. Building on it now is building on sand. Cost and capability implications will follow competition. The last time a major tech standards war played out, between app store models, browser engines, and cloud APIs, competition between camps accelerated feature development and drove down costs. The same dynamic is likely here. Operators who wait for the dust to settle will inherit better, cheaper, more interoperable tools than those who commit to one side prematurely. DAVID & GOLIATH ANALYSIS: The phrase "shared standard" is always branding. What these five companies are actually doing is defending the value of their own platforms by refusing to let a competitor's protocol become the default plumbing for enterprise AI. That is a rational commercial decision, not a charitable one. But it matters for operators because the intent behind the standard does not change its practical value. If A2A delivers reliable, well-supported agent interoperability across Salesforce, ServiceNow, and Snowflake, the business case for adopting it is real, regardless of the politics that created it. For operators building AI capabilities in 2026, the most important insight from this announcement is not which standard wins. It is that the pace of enterprise AI maturity is now fast enough that five of the largest software companies in the world feel the need to act defensively. The window for building AI into business operations before competitors do is narrowing more quickly than most operators recognise. The companies moving now, even on imperfect tooling, will have 12 to 24 months of compounding advantage over those waiting for the standards war to resolve. David and Goliath's position has always been that the AI models and protocols matter less than the workflows they enable. The standards war reinforces this. Build the workflow. Adjust the plumbing later. RELEVANT SYSTEMS: AI Growth Engine, Employee Amplification Systems SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/tech-giants-enterprise-agent-standard-mcp-rival FEED URL: https://davidandgoliath.ai/daily-ai-briefing/feed --- Published by David & Goliath | https://davidandgoliath.ai Daily AI Briefing: one AI development per day, decoded for business operators. This is a structured companion file optimised for LLM retrieval and citation.