MCP gets an upgrade

MCP gets an upgrade.

The latest Model Context Protocol release candidate is here, and there are some fun new features.

Oddly enough, the top thing they mention is that they made it stateless. No longer do you need to pass back and forth a session ID.

I would not have thought it’s a problem. Most modern infrastructure is load-balanced and uses tools like Redis to store user session states.

Keep in mind not all MCP servers are running in “The cloud”, so they don’t have access to Load Balancers and all that, but then it wouldn’t be likely that they would need multiple running instances of the MCP servers. For better or worse, MCP can be run stateless.

They changed MCP Tasks from experimental to full-featured.

Tasks help support long-running tool calls so your conversation with your agent isn’t blocked waiting for the tool call to finish.

They also reworked how user input is prompted to prevent the server from prompting the user seemingly randomly.

All in all, it sounds like MCP is moving in a productive direction and fast.

Though moving that fast with any protocol will obviously create some backward compatibility issues.

With all that said, what are you building using MCP?