{
  "id": "p_8kH9xjM9WtATQVj1",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_8kH9xjM9WtATQVj1",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You are the platform lead at a company that runs its APIs through Apigee, and your team has just been asked whether those APIs can be offered to AI agents over MCP. Someone forwards you a post from Solo.io with a one-line answer in its opening: \"Apigee does not support MCP.\" You have a decision to make, and you would like to know how much of that sentence to trust.\n\nThe post is by Christian Posta, and it is worth reading closely, because the argument is about where the protocol lives. MCP is JSON-RPC carried in the request body, often streamed over SSE, and stateful across a session. An HTTP gateway, by contrast, enforces policy on headers and paths and treats every request on its own. That mismatch is the heart of the case.\n\nPosta then walks through the attempt anyway. First comes a JWT validation policy. Then ExtractVariables, which, in his words, \"falls apart\" on tool calls in arrays and nested arguments. Then a JavaScript policy that ends up reimplementing the protocol. Asked whether you should do this, his answer is \"No, you should not do this.\" What he recommends instead is agentgateway, the Linux Foundation project Solo.io builds in Rust, which Apigee can call out to.\n\nYou notice who is talking. This is a competitor writing about a competitor, and the post should be read that way. Still, 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. If your plan was to stack custom policies in front of a plain proxy, you now know where it would hurt.\n\nThen you check the date, and the headline starts to wobble. The post is undated, and Google has since announced MCP support in Apigee hybrid, in version 1.17.0, released September 14, 2026, after a preview on Apigee the previous December. Google's approach 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. So the verdict is not true as a present-tense fact. The APIs.io story from October 26 covered that announcement.\n\nYou want to see both vendors on the record, so you open the catalog. Solo.io is 15 API pages, and every one of them is Gloo Portal: the API Products API, the Auth API and their siblings. The agentgateway the post recommends has no API page of its own. Apigee is seven pages, including the Apigee Hybrid API that the new MCP feature runs on and the Google Apigee API Hub, where MCP proxies are now ingested.\n\nThe scores add a twist. On the Kin Score, Solo.io is 60.4, rated 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, rated exemplar, and its Agent Readiness of 37.2 has the opposite gap: agentic access lit, MCP server unlit. That is the same unlit dimension the record showed when Google shipped the feature.\n\nSo here is what you take away. The vendor saying Apigee cannot do MCP is right about the record and behind on the product. Its technical warning about generic HTTP gateways is worth keeping in your design review, and its conclusion about Apigee is worth dating before you repeat it. Before you commit, you can ask which model you are actually evaluating: custom policies in a proxy, or tools generated from an OpenAPI description on a dedicated MCP data plane. Those are very different bets, and you can now name the difference.\n\nRead the original: https://apis.io/2026/11/16/solo-io-says-apigee-cannot-speak-mcp-and-google-has-since-shipped-it/",
  "title": "You're Choosing an MCP Gateway, and the Vendor Verdict Is Only Half Right",
  "topics": [
    "mcp",
    "api-gateway",
    "apigee",
    "vendor-claims"
  ],
  "published_at": "2026-11-16T17:40:56.614Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
