Apigee hybrid 1.17.0 发布:MCP 支持落地自有 Kubernetes 集群
Apigee hybrid 1.17.0 于 2026 年 9 月 14 日发布,Model Context Protocol 支持进入 Apigee hybrid,MCP 数据平面运行在用户自己的 Kubernetes 集群内,MCP 请求流量不离开集群。用户用 OpenAPI 3.0.x 规范创建 MCP Discovery Proxy,每个操作即一个 MCP 工具,无需编写 MCP 服务器代码;该功能默认关闭,需在 overrides.yaml 中设置 enableMcpServer: true 并依次升级 apigee-operator 与 apigee-org chart。

rety in one global view. (Assumption is all services (Apigee/Non-Apigee) in the chain report to the same Google CloudTrace) MCP clients carry W3C trace context inside the JSON-RPC meta field, which a conventional REST backend has no idea how to read. Apigee extracts it and forwards it as ordinary traceparent and tracestate headers, so instrumented services downstream join the trace without code changes. Three things follow: a single trace ID spanning the AI client, the Apigee proxies and backend
匹配字段正文
