/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Google DeepMind CEO Demis Hassabis says Google will add support for Anthropic's Model Context Protocol to its Gemini models and SDK, but did not give a timeline

Just a few weeks after OpenAI said it would adopt rival Anthropic's standard for connecting AI models to the systems where data resides, Google is following suit.

TechCrunch Kyle Wiggers

Context & Ripple Effects

Google has been building Gemini for long-context and developer use cases, including its earlier Vertex AI preview with a 1M-token context window. Adding Anthropic's protocol shifts attention from how much context Gemini can hold to how consistently it can connect with external data and tools.

The move also fits Google's broader agent ambition, later visible in Gemini CLI's connection to local codebases. Here, Google is signaling that interoperability can matter alongside control of the model and SDK stack.

First-order effects

  • Developers using Gemini models and Google's SDK will eventually be able to use Model Context Protocol rather than build solely to Google's proprietary integration patterns; Google gave no rollout date.
  • Anthropic's protocol gains a major additional implementation commitment, making it more practical for tool and data-system providers to consider MCP support.

Second-order effects

  • Tool, data, and developer-platform vendors can reduce the cost of supporting multiple leading model ecosystems if Gemini's implementation is compatible with other MCP adopters.
  • Google's SDK becomes more competitive for agentic applications whose builders want to preserve model choice, rather than lock integrations to one model provider.

Third-order effects

  • If major model vendors converge on MCP, the integration layer around AI agents could become more standardized while competition shifts toward model quality, distribution, and proprietary data access.
  • The remaining uncertainty is implementation: an announced commitment without a timeline does not yet establish how portable Gemini-based MCP workflows will be in practice.

The trend: AI model providers are increasingly competing to become interoperable agent platforms, not just providers of proprietary model APIs.

Discussion

  • @demishassabis Demis Hassabis on x
    MCP is a good protocol and it's rapidly becoming an open standard for the AI agentic era. We're excited to announce that we'll be supporting it for our Gemini models and SDK. Look forward to developing it further with the MCP team and others in the industry
  • @sundarpichai Sundar Pichai on x
    love the feedback! - to MCP it is!