MCP CHANGED · Agent Zero

MCP CHANGED

### MCP: What Changed and What’s the Advantage?

**Before: MCP needed to maintain a session and “remember” each user between calls. This made the infrastructure more complex and could require persistent sessions, Redis, sticky sessions, and tighter control over which server handled each user.

**Now: each request can be independent. The client sends the necessary context with every call and, when a process needs to continue, it can use a secure identifier — similar to the “restaurant tab” analogy used in the original explanation.

In practice:

```text

BEFORE

User → session → specific server → keeps state

NOW

User + context → any server → response

```

### The Main Advantage

For developers:

* less complexity;

* simpler deployment;

* less dependency on session infrastructure;

* better use of serverless and edge environments;

* easier scaling;

* simpler retries and load balancing.

For users, almost nothing changes in the interface. The difference happens behind the scenes: the system can become more scalable, resilient, and cheaper to operate.

In one sentence:

> MCP is moving away from a conversation tied to a specific server and becoming more like a modern HTTP API: simple, independent, and easy to scale.

And that matters because it makes it much easier to turn existing APIs, systems, and tools into capabilities that AI agents can use.

https://modelcontextprotocol.io/specification/2026-07-28/changelog

0 comments

MCP CHANGED