Executive TL;DR:

• Stateless MCP is gaining traction as a more efficient alternative to traditional MCP.
• Forum voices highlight the potential benefits of stateless MCP, including reduced context bloat and improved scalability.
• The shift towards stateless MCP may simplify infrastructure and reduce maintenance costs.

The Buzz Score

The Internet’s Verdict: 70% Hyped, 30% Skeptical

Forum Voices

Developers and users are weighing in on the potential of stateless MCP. As one user notes:

I think stateless-type MCP was already possible, eg my MCP Clock: curl -s -X POST “https://mcpclock.firasd.workers.dev/mcp” -H “Content-Type: application/json” -H “Accept: application/json, text/event-stream” -d ‘{“jsonrpc”:”2.0″,”id”: 1,”method”:”tools/call”,”params”:{“name”:”clock_get”,”arguments”:{}}}’ | grep ‘^data:’ | sed ‘s/^data: //’| jq

Others are highlighting the limitations of traditional MCP. For example:

In retrospect, stateful MCP was clearly wrong. This essentially makes MCP just another REST API endpoint, and lets you use the same infrastructure you already have set up for REST APIs (like load balancers, API gateways, progressive rollouts, etc).

Another user notes the issue of context bloat with traditional MCP servers:

My main issue with MCP servers has been context bloat. Skills have progressive disclosure, and allow me to turn off auto invocation with something like this in the SKILL.md file: disable-model-invocation: true Most MCP servers still bloat up my context even when I am not using them at all. Why can’t they be configured to allow me to keep them out unless I really need to use them?

Focus Keyword: Stateless MCP