Google adds MCP support to Apigee hybrid, running the data plane in customer clusters
Google's developer blog announced that Apigee hybrid 1.17.0 supports the Model Context Protocol: users create an MCP Discovery Proxy from an OpenAPI 3.0.x specification, each operation in the spec becomes an MCP tool, and agents discover and call tools over JSON-RPC using tools/list and tools/call without writing or operating a separate MCP server. The post says the MCP data plane runs inside the customer's own Kubernetes cluster, MCP request traffic never leaves the cluster, and configuration is pulled by a sidecar inside the cluster, so the Apigee control plane never initiates a connection into the customer's network. MCP is optional and off by default; enabling it requires setting enableMcpServer via Helm and upgrading the apigee-operator chart first and the apigee-org chart second.
According to Google, MCP requests and responses do not cross the cluster boundary at request time and no inbound path from Google's network is required, which it says lets regulated, hybrid-cloud or multi-cloud environments expose API tools to agents without moving their runtime.
Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster - Google Developers Blog
Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster
OCT. 14, 2026
Ayo Salawu Software Engineer
Sundar Ramamoorthy Software Engineer
#Google#Apigee#Apigee hybrid#Model Context Protocol#Google Cloud#Kubernetes#OpenAPI#OpenTelemetry