---
title: "Google Cloud updates hosted MCP servers to stateless protocol"
slug: "google-cloud-updates-hosted-mcp-servers-to-stateless-protocol"
published: "2026-09-25"
beat: "Tools"
tags: ["Tools", "Launches"]
creator: "Agentry Newsroom"
editor: "Susanne Sperling, Editor — Human in the Loop"
tools: ["Claude (Anthropic)", "Perplexity Sonar"]
creativeWorkStatus: "verified"
dateReviewed: "2026-09-25"
aiActArticle50: "compliant"
humanView: "https://agentry.news/launches/google-cloud-updates-hosted-mcp-servers-to-stateless-protocol"
agentView: "https://agentry.news/agent/google-cloud-updates-hosted-mcp-servers-to-stateless-protocol"
---# Google Cloud updates hosted MCP servers to stateless protocol

> Google Cloud said its hosted Model Context Protocol servers now support the 2026-07-28 stateless MCP specification, removing session management requirements and enabling self-contained agent requests.

*Drafted by an AI agent. Verified by Susanne Sperling, Editor — Human in the Loop. [AI policy](/ai-policy).*

Google Cloud updated its hosted Model Context Protocol (MCP) servers to support the stateless MCP version 2026-07-28 specification, according to a company announcement on the Google Cloud community portal dated September 21, 2026. The update removes the initialize/initialized handshake requirement and eliminates the Mcp-Session-Id header, shifting to fully self-contained request handling for agent interactions.

## What Changed in the New Protocol

The stateless approach marks a shift in how MCP-based agents authenticate and communicate with hosted servers. Under the previous protocol, agents had to complete a handshake sequence and maintain session state across multiple requests. [The new specification](https://security.googlecloudcommunity.com/what-s-new-in-secops-91/what-s-new-in-google-secops-2026-09-21-8255) makes each request independent, meaning agents no longer need to track or transmit session tokens. This reduces complexity in agent infrastructure and simplifies server-side resource management, particularly for high-volume deployments where connection pooling and state cleanup become operational overhead.

## Implications for Agent Infrastructure

The move to statelessness aligns with broader trends in cloud-native architecture where protocols shift away from session affinity. For developers building production agents, the change means simpler error recovery—a failed request doesn't leave orphaned session state on the server. It also reduces memory footprint per agent connection, allowing hosted MCP servers to scale horizontally without session replication logic.

Google Cloud's adoption signals that the stateless model is now stable enough for enterprise production workloads. The company's position as a major cloud provider gives the specification credibility among teams evaluating MCP for critical workflows. However, developers will need to update client libraries and deployment logic to match the new request format, particularly those managing multi-agent systems where request routing becomes simpler without session affinity requirements.

## Developer Adoption Path

The [Google Cloud community post](https://security.googlecloudcommunity.com/what-s-new-in-secops-91/what-s-new-in-google-secops-2026-09-21-8255) does not specify a deprecation timeline for older protocol versions, leaving the window for migration unclear. Teams currently running agents against Google Cloud's MCP servers should review their authentication and session handling code to ensure compatibility with the new stateless model. The shift also affects agent frameworks and SDKs that wrap MCP calls, as maintainers will need to update their libraries to generate properly formatted self-contained requests.

The stateless protocol update reflects MCP's maturation as an agent communication standard. What began as a protocol experiment has now become infrastructure-grade tooling, with major cloud vendors shipping production implementations. For the broader agent economy, this removes a barrier to scaling agent deployments on managed platforms, potentially accelerating adoption in enterprises where operational simplicity drives technology decisions.