Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-15 · source-backed
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 14-day window.
This is the moment MCP stopped being "Anthropic's protocol" and became the industry standard for agent-to-application communication. The same way REST APIs became how apps talk to each other, MCP is becoming how agents talk to everything else.
The convergence is striking because these platforms didn't coordinate. Notion, ServiceNow, Figma, and Google made independent decisions to implement the same protocol at roughly the same time. That's a signal of inevitability, not collaboration. Each of them looked at the agentic ecosystem and concluded: if AI agents can't see our product, we're invisible.
Google's implementation is particularly notable. Their new Workspace CLI, written in Rust and already at 26.2K stars, includes built-in AI agent skills. Combined with the Workspace MCP Server and the new AI Control Center for enterprise governance, Google shipped a complete agentic stack: agents can synthesize Drive documents, draft Gmail responses, manage Calendar, all within SSO and DLP controls.
Salesforce released a Data 360 MCP server in developer preview that consolidates roughly 200 REST API operations behind three facade tools with intent-based search. Instead of exposing individual endpoints, they're giving agents a semantic interface to the entire platform.
For SaaS builders, the message is clear: MCP support is table stakes. If your product doesn't expose an MCP server, AI agents can't interact with it. Users are choosing tools based on what their agent can access. The REST API parallel is instructive: companies that were slow to build REST APIs in 2010 lost developer mindshare they never recovered.
Build your MCP server. Do it this month.
Each link below shares sources, entities, or timing with this story.
Gmail built by Google / Shared entities / Same source / Shared topic / What happened next
Linked by a graph relationship (Gmail built by Google); both cover Calendar, Drive, Gmail, Google; cite the same source (Workspace CLI).
Cursor supports Gmail / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor supports Gmail); both cover Anthropic, Build, Calendar, Combined; reported by the same outlet (notion.com).
Gmail built by Google / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Gmail built by Google); both cover Calendar, Drive, Gmail, Google; overlapping topics (agent, developer, google).
Gmail built by Google / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Gmail built by Google); both cover Anthropic, Google, MCP, Salesforce; overlapping topics (agent, same).
Cursor supports Gmail / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor supports Gmail); both cover Anthropic, Build, MCP, Notion; reported by the same outlet (notion.com).
Gmail built by Google / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Gmail built by Google); both cover Gmail, Google, Their; reported by the same outlet (github.com).
Gmail built by Google / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Gmail built by Google); both cover Anthropic, Google, Notion, Salesforce; overlapping topics (control, same, their).
Gmail built by Google / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Gmail built by Google); both cover Anthropic, Google, MCP; reported by the same outlet (github.com).