Key points
- Apigee Hybrid 1.17.0 introduces native Model Context Protocol support for on-premises and multi-cloud Kubernetes deployments.
- The architecture ensures that all AI agent request traffic and tool execution remain strictly inside the customer’s own infrastructure.
- Configuration updates are pulled from the Google Cloud control plane, requiring no inbound connections from Google into the customer network.
Google announced on 14 September 2026 that Apigee Hybrid 1.17.0 includes native support for the Model Context Protocol, allowing the data plane to operate directly within a customer’s Kubernetes cluster.confirmed This release addresses infrastructure constraints where runtime must reside in specific data centres or clouds.
Evidence: confirmed
Announcing MCP support in Apigee hybrid: agentic tools that run in your own clusteraifleet-google-dev
The claim
According to the Google Developers blog post, the update enables organisations to run MCP tool execution entirely inside their own infrastructure.reported The system pulls configuration updates from the central control plane but processes all agent requests locally. This design ensures that no MCP request or response crosses the boundary to Google Cloud during execution.
Evidence: reported
Announcing MCP support in Apigee hybrid: agentic tools that run in your own clusteraifleet-google-dev
The response
The blog post notes that customers immediately asked whether agentic access could be provided without moving their runtime infrastructure. Many organisations require data to stay in specific facilities or jurisdictions due to regulatory mandates or multi-cloud realities. The new feature responds to this demand by keeping the runtime where the systems of record already exist.
The bottom line for teams
Teams can now expose OpenAPI 3.0.x specifications as discoverable MCP tools without writing custom server code.reported The architecture reuses existing Apigee identities and security policies. Configuration is fetched periodically by a sidecar, meaning Google’s control plane never initiates connections into the customer’s cluster.
Evidence: reported
Announcing MCP support in Apigee hybrid: agentic tools that run in your own clusteraifleet-google-dev
What the paper shows
The blog post details how Apigee Hybrid 1.17.0 handles Model Context Protocol traffic within customer-owned Kubernetes environments.reported It reports that the MCP data plane runs locally, keeping agent requests inside the cluster while pulling configuration from the control plane.reported The stated limitation is that this requires the specific 1.17.0 release. The material confirms that tool discovery and invocation use standard JSON-RPC methods, with Apigee managing the protocol transcoding.
Evidence: reported
Announcing MCP support in Apigee hybrid: agentic tools that run in your own clusteraifleet-google-dev
Evidence: reported
Announcing MCP support in Apigee hybrid: agentic tools that run in your own clusteraifleet-google-dev
Why it matters
- Model evaluators can verify that agent tool calls do not traverse external networks, satisfying strict data residency requirements.
- The reuse of existing API products and security policies allows teams to apply familiar governance controls to agentic workloads.
- The pull-based configuration model eliminates the need for inbound firewall rules from Google Cloud, simplifying network security reviews.
- Support for Data Residency-enabled organisations ensures that sovereignty constraints are met by architecture rather than manual configuration.
Topics: Apigee, Model Context Protocol, Kubernetes, AI Agents, Google Cloud
Updated
Ask the article
Local keyword search of this article; no generated answers.Which of these is confirmed?
Check the answer
Google announced on 14 September 2026 that Apigee Hybrid 1.17.0 includes native support for the Model Context Protocol, allowing the data plane to operate directly within a customer’s Kubernetes cluster.
The matched primary source and announcement wording support the confirmed label.
Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
Does Apigee Hybrid 1.17.0 require new IAM roles for MCP support?
No, the MCP sidecar reuses the existing apigee-watcher identity, so no new service accounts or IAM roles are required.
Can agents discover tools in an Apigee Hybrid cluster?
Yes, agents can use the tools/list method over JSON-RPC to discover available tools derived from OpenAPI 3.0.x specifications.
Does MCP traffic leave the customer's cluster?
No, the blog post states that MCP request traffic stays inside the cluster and never crosses the boundary to Google Cloud.
Connected stories
Reading receipt
- Apigee Hybrid 1.17.0 introduces native Model Context Protocol support for on-premises and multi-cloud Kubernetes deployments.
- The architecture ensures that all AI agent request traffic and tool execution remain strictly inside the customer’s own infrastructure.
- Configuration updates are pulled from the Google Cloud control plane, requiring no inbound connections from Google into the customer network.