The MCP data plane runs inside the customer's Kubernetes cluster. Teams can derive an MCP Discovery Proxy from an OpenAPI 3.0.x specification; each operation becomes a discoverable tool, exposed through JSON-RPC tools/list and tools/call. Google says MCP request and response traffic stays within the cluster, while a sidecar fetches tool configuration from the Apigee control plane; that control plane does not initiate an inbound connection into the cluster. The feature is optional and must be enabled on a cluster running version 1.17.0 or later. MCP endpoints inherit Apigee proxy controls, including API products and existing security policies.
Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster
In one minute
Google announced native Model Context Protocol support in Apigee hybrid 1.17.0, released September 14, 2026.