The Model Context Protocol launched in November 2024. Two years later, the most common objection we hear from SaaS teams isn't "do our customers want this?" It's "what will it cost us to run?"

The latest version of the spec answers most of that.

Is your SaaS agent-ready? Get your score

What changed in 2026-07-28

The MCP specification released on July 28, 2026 rebuilt the protocol around a stateless core. The MCP team's own summary: MCP is "transforming from a bidirectional stateful protocol into a request/response stateless protocol." (MCP Blog)

In practice:

  • No handshake, no sessions. The initialize exchange and the Mcp-Session-Id header are gone. Every request carries its own protocol version and client details.
  • Any request can land on any server. According to the MCP team, requests can now go to any instance "behind a plain round-robin load balancer without needing shared storage."
  • No long-held connections. Each message is its own HTTP POST to a single endpoint such as /mcp, and the always-open stream for server messages has been removed. (MCP spec: Streamable HTTP)
  • Routing works from headers. Method and tool names travel in HTTP headers, so gateways can route and authorize requests without reading the body.

The MCP team says this was one of the most requested changes from developers who wanted better reliability and scaling.

Why that makes hosting cheap

A stateless server is exactly what serverless platforms are built for. When no session has to live in memory between calls, your MCP endpoint can run as a function that starts on demand, scales with traffic and costs nothing when nobody is using it. You don't need sticky sessions, a session store or a fleet of always-on servers.

For most SaaS products, that means an MCP server can run on the same serverless setup as the rest of the API.

The enterprise side is ready too

On October 16, Red Hat made its MCP gateway for OpenShift generally available as part of Red Hat Connectivity Link 1.5. It routes, secures and governs MCP traffic, and the GA release added stateless session support along with guardrails and tenant isolation. (Red Hat)

That matters if you sell to larger companies. Their platform teams now have production-grade tooling to approve, route and audit MCP servers, including yours.

The excuse is gone

The cost of running an MCP server has dropped, and big buyers have tooling to adopt one. The real cost now is not having one: customers' agents can't reach your product, so the work goes to tools they can reach. That's ghost churn, and it doesn't show up until renewal.

See where your product stands

Our free Agent Readiness Check scans your site for the signals AI agents look for, including a discoverable MCP server, and scores you in about a minute.

Run the free Agent Readiness Check

Is your SaaS agent-ready? Get your score

Run a free Pryno readiness check on your MCP server