# Apigee Hybrid adds MCP support to run AI tools in your own Kubernetes cluster

> Google released Apigee hybrid 1.17.0 on Sep 14 2026, letting the Model Context Protocol data plane run inside customers' clusters.

Oossa · 2026-10-14 · https://oossa.com/en/apigee-hybrid-adds-mcp-support-to-run-ai-tools-in-your-own-kubernetes-cluster

Google announced that Apigee hybrid version 1.17.0 now includes Model Context Protocol (MCP) support. The MCP data plane runs inside the user's Kubernetes cluster, so AI agents can call APIs without traffic leaving the customer's infrastructure. The feature works the same way as the cloud version—API specs are described with OpenAPI, tools are discovered via JSON‑RPC, and Apigee handles security—but the processing happens on‑premises. Enabling MCP is optional and done through a Helm chart upgrade.

## The facts

- Apigee hybrid 1.17.0 released on September 14, 2026
- MCP traffic stays inside the customer’s cluster and is fetched, not pushed

## Why it matters

Enterprises with data‑ residency or multi‑cloud constraints can now expose their APIs to AI agents without moving workloads to Google Cloud.

## Sources & references

1. [Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster](https://developers.googleblog.com/en/announcing-mcp-support-in-apigee-hybrid-agentic-tools-that-run-in-your-own-cluster/) – Google for Developers

Last updated: 2026-10-14