Fetching from the wire…
Top 5 · 2026-07-14 · source-backed
For 18 months, Anthropic's Model Context Protocol has been the thing everyone quietly agreed on. You want to plug a tool into an agent, you speak MCP. It won by being early, open, and good enough. That consensus is now contested. Per The Information, Google, Microsoft, Salesforce, Snowflake, and ServiceNow agreed to back a common AI backend-software protocol, framed explicitly as a counter to MCP (Crypto Briefing).
Read the roster again. Those five own most of the enterprise data, most of the workflow surfaces, and a big chunk of the cloud your agents run on. This isn't a startup floating an RFC nobody adopts. When Salesforce and ServiceNow decide what protocol their platforms speak natively, that decision propagates into thousands of enterprise stacks by default.
The part I can't stop thinking about: the same companies also co-participate in the Linux Foundation's Agentic AI Foundation. So they cooperate in the foundation and knife-fight on the protocol layer at the same time. That's not hypocrisy, it's how standards wars actually work. You keep a seat at the neutral table so you're not caught out, and you push your own thing where the leverage is.
For builders, the annoying truth is you now have a protocol bet to make, and the "safe" default got less safe. If you wired everything to MCP because it was the obvious standard, you're fine today and exposed in a year. My read: keep building on MCP, because it has real adoption and the tooling exists, but abstract your tool layer so a protocol swap is a config change, not a rewrite. Treat the connection protocol like you'd treat a database driver. You don't hardcode your app to Postgres wire format. Don't hardcode your agent to one tool protocol either.
The bigger signal is that "connect a tool to an agent" is now valuable enough that the incumbents want to own the pipe. That only happens when the category is real. Watch whether this alliance ships a spec with working SDKs or just a press release. The first tells you it's a threat. The second tells you it's a hedge.
Each link below shares sources, entities, or timing with this story.
If you wrote an MCP server before July, it's on a protocol shape the maintainers have already removed. Not deprecated-with-a-migration-window. Removed from the spec. MCP lead maintainers David Soria Parra and Den Delimarsky published an updated roadmap on August 22, and the re...
AAIF will govern MCP, Block's Goose, AGENTS.md, and Google's A2A under vendor-neutral open governance. AWS, Cisco, Google, Microsoft, Salesforce, SAP, and ServiceNow are participating. Both inter-agent communication and tool access protocols now have neutral stewardship. Linux...
The agent business model showed up this week, and it's rent. At Knowledge 2026, ServiceNow launched Action Fabric, a layer that every external AI agent must pass through to read data or run workflows inside the ServiceNow platform, metered on action-based pricing (ServiceNow N...
Notion's Developer Platform 3.5 on May 13. ServiceNow Action Fabric MCP Server on May 5. Figma's agentic design via MCP in their May release. Google Workspace MCP Server in preview. Four platforms serving hundreds of millions of users, all shipping production MCP support in a...
BlueRock scanned over 7,000 MCP servers against 22-plus security rules. 36.7% carry potential server-side request forgery exposure from unrestricted outbound fetch, and 42% handle credentials insecurely. Their worked example is Microsoft's 85K-star Markitdown MCP server and it...
Microsoft, Adobe, SAP, Salesforce, PayPal, ServiceNow. The three-protocol stack (A2A + MCP + WebMCP) is becoming standard enterprise plumbing. Google Cloud Blog
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.