Christian Posta’s post on building an MCP gateway with Apigee opens with a flat verdict: “Apigee does not support MCP.” The argument is about where the protocol lives. MCP is JSON-RPC in the request body, often streamed over SSE, and stateful across a session, while an HTTP gateway enforces policy on headers and paths and treats every request on its own. Posta walks the attempt anyway, a JWT validation policy, then ExtractVariables, which “falls apart” on tool calls in arrays and nested arguments, then a JavaScript policy that ends up reimplementing the protocol. His answer to whether you should do this is “No, you should not do this,” followed by agentgateway, the Linux Foundation project Solo.io builds in Rust, which Apigee can call out to.
This is a competitor writing about a competitor, so read it as one. The technical points hold for a generic HTTP gateway: no session persistence, no notion of which capabilities a session negotiated, and authorization logic living in custom code. The headline does not hold as a present-tense fact. The post is undated, and Google has since announced MCP support in Apigee hybrid in 1.17.0, released September 14, 2026, after a preview on Apigee the previous December. Google’s model sidesteps Posta’s objection rather than refuting it: Apigee generates the MCP tools from an OpenAPI description and runs a dedicated MCP data plane, not JavaScript in a proxy. We covered that announcement on October 26.
Both sides are in the catalog. Solo.io is 15 API pages, and every one of them is Gloo Portal: the Solo.io API Products API, the Solo.io Auth API and their siblings. The agentgateway this post recommends has no API page of its own. Apigee is seven, including the Apigee Hybrid API the new MCP feature runs on and the Google Apigee API Hub that MCP proxies are now ingested into.
On the Kin Score, Solo.io is 60.4, strong, led by developer ergonomics at 78.6, with access clarity at 50.0 and contract governance at 28.0. Its Agent Readiness is 34.8, with an MCP server lit and agentic access unlit. Apigee is 68.0, exemplar, and its Agent Readiness of 37.2 has the opposite gap: agentic access lit, MCP server unlit, the same unlit dimension the record showed when Google shipped the feature. The vendor saying Apigee cannot do MCP is right about the record and behind on the product.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.