Google says Apigee hybrid 1.17.0, released September 14, 2026, runs the MCP data plane inside the customer’s Kubernetes cluster. An OpenAPI 3.0.x specification can generate an MCP Discovery Proxy whose operations are exposed as tools through JSON-RPC discovery and calls.
First implication: Platform teams can evaluate agent access to existing APIs without treating migration to Google-managed runtime as a prerequisite. First watch condition: Whether operators can enable and govern this optional feature reliably across real hybrid deployments, including its staged canary rollout and configuration-fetch behavior.
Thesis
Deployment location is part of the agent integration contract: teams can expose APIs as MCP tools without moving request execution out of the infrastructure where those APIs already run.
Observed facts
Apigee hybrid 1.17.0, released September 14, 2026, adds MCP support with the data plane running inside the customer's Kubernetes cluster.
1An OpenAPI 3.0.x specification can generate an MCP Discovery Proxy whose operations are exposed as tools through JSON-RPC discovery and calls.
1The announcement says request and response traffic stays within the cluster while a sidecar pulls configuration from the Apigee control plane.
1
Mechanism
The cluster-side data plane serves MCP requests locally; a sidecar fetches tool configuration from the control plane, which does not initiate an inbound connection into the cluster. Existing Apigee proxy controls, including API products, apply.
Why now
The release extends Apigee's existing MCP approach to hybrid customers whose runtime is intentionally on-premises, in another cloud, or in a regulated environment.
Implications
Platform teams can evaluate agent access to existing APIs without treating migration to Google-managed runtime as a prerequisite.
Teams can apply existing Apigee governance to agent-facing tools, subject to their deployment and authorization configuration.
Evidence boundary
The vendor announcement describes architecture and setup, but supplies no independent deployment results, latency comparisons, or customer outcome measurements.
Watch conditions
Whether operators can enable and govern this optional feature reliably across real hybrid deployments, including its staged canary rollout and configuration-fetch behavior.