Google has taken Apigee’s MCP support to the customers whose runtimes cannot move. In Announcing MCP support in Apigee hybrid, the post explains that last December’s preview turned existing APIs “secured, governed and cataloged” into tools agents can call “without writing code or standing up MCP servers of your own,” and that the first question back was “can I have this where my runtime actually lives?” With Apigee hybrid 1.17.0, released in September, “the MCP data plane runs inside your own Kubernetes cluster.”
There are no adoption figures, and the two properties a security review will ask about are stated plainly. “MCP request traffic stays inside your cluster”: an agent’s tools/call is received, authorized and proxied entirely within the customer’s infrastructure. And “configuration is pulled, not pushed”: a sidecar fetches the tool configuration from the control plane, so “MCP requires no inbound path from Google into your network.” The model is otherwise unchanged: describe an API in OpenAPI 3.0.x, create an MCP Discovery Proxy, and “every operation in that spec becomes an MCP tool.” Governance carries over because MCP endpoints are Apigee proxies, so OAuth, OpenID Connect, API keys and the policy library apply, and the API product lists which tools a client may call, with an optional per-tool quota. The post is honest about the operational edge: upgrade the charts in the wrong order and you get “a successful upgrade with no MCP pods.”
The catalog holds Apigee’s management surface in depth. The Apigee provider page lists 45 API pages, and the post’s design rests on the Apigee API Products API, where tool entitlements and quotas live, the Apigee API Proxies API that MCP Discovery Proxies are built from, and the Apigee API Specs API that holds the OpenAPI they start from. The agentic access profile maps 179 operations, 101 of them acting.
The Kin Score is 66.9, exemplar band, with discoverability at 85.7 and developer ergonomics at 82.1 against contract governance at 18.2. The Agent Readiness score is 29.8, agent-ready. The MCP server dimension is unlit, on the record of a product whose release is about turning every customer’s API into an MCP server. The likely reason is the one this series has found three times this month, with AWS, Kong and Atlassian: the probe looks for a server at the company’s own address, and Apigee’s MCP endpoints live at each customer’s. Apigee has made every API it manages agent-callable without new code. The catalog needs a way to credit a company for the MCP servers it runs for others.