MCP Becomes the Plugin Standard

Google shipped Gemini MCP-client support last week. The call we made in 2024-W26 and refined in 2024-W46 has landed. The protocol war is over inside twelve weeks of the start of 2025. The frameworks the industry was supposed to fight over (AutoGen, CrewAI, ChatDev) are now in a visible repositioning cycle, all of them coalescing as MCP clients rather than as competitors.

What changed in the last twelve weeks

Three concrete things.

Google's Gemini SDK now ships MCP-client support out of the box. This is the inflection point. Once Google adopts a standard, the rest of the market reads it as inevitable.

The public Anthropic MCP server directory crossed 2,800 implementations in mid-February. Categorical growth is roughly 50% month over month since November.

The major framework projects (LangChain, AutoGen, CrewAI) have all shipped MCP-client documentation in the last six weeks. They are no longer pitching themselves as plugin alternatives. They are pitching themselves as orchestration layers above MCP.

The remaining holdout

OpenAI has not shipped MCP-client support and will likely resist through Q2. The internal pressure to push the existing function-calling schema is real. The market pressure to support MCP is larger. We expect formal OpenAI MCP-client support by end of Q3.

What this unlocks for the Gulf

This is the piece most under-priced by GCC enterprise procurement teams.

The Falcon and Jais releases coming out of TII and MBZUAI now ship into a global tool ecosystem rather than into a Falcon-specific plugin world. Every server in the Anthropic MCP directory is addressable by a Falcon-driven client. Every Jais-driven workflow inherits the global integration library.

The DIFC AI license framework has, separately, been quietly standardizing on MCP as the integration reference. We expect this to be formal by end of Q2. Once it is, every DIFC-licensed AI vendor will be expected to ship MCP-compliant tooling as a default compliance checkbox. That posture eliminates roughly half of the contractual ambiguity that has slowed AI procurement at Emirates NBD, ADCB, and FAB through 2024.

For Saudi, the SDAIA framework will follow with a six-month lag. We expect the SAMA agentic-banking framework (forecast in 2026-W12) to adopt MCP as the reference shape.

What this means for the Gulf

The protocol question is settled. Operators still building proprietary integrations against single-vendor plugin formats are building technical debt that they will pay for inside twelve months. The right move is to convert internal-tool integrations into MCP servers now, and to spec all new AI procurement around MCP-shaped deliverables.

Zanii will publish MCP server templates for GCC banking, healthcare, and government use cases through Q2. The /track-record page tracks the running grade. This call verified faster than we modeled. The window to be early on the operational consequences closes by mid-year.