MCP 2026-07-28 Specification: transport going stateless(blog.modelcontextprotocol.io)
72 pointsby Eldodi3 hours ago14 comments
  • punkpeye41 minutes ago
    Finally.

    I am running an MCP server gateway/registry (some of you may know Glama).

    I cannot tell you what portion of our issues/bugs were due to the need to persist server state.

    This change will allow us to offer a lot easier way for people to use Open-Source MCP servers.

    • punkpeye10 minutes ago
      Just ran some quick numbers. In our index of 62,726 Open-Source servers, ~18,000 have been pushed to in the last 30 days.

        ┌─────────────────────────────┬────────┬───────────┐
  │ Pushed in last 7 days       │ 6,101  │ 9.9%      │
  ├─────────────────────────────┼────────┼───────────┤
  │ Pushed in last 30 days      │ 18,707 │ 30.2%     │
  ├─────────────────────────────┼────────┼───────────┤
  │ Pushed in last 90 days      │ 30,393 │ 49.1%     │
  ├─────────────────────────────┼────────┼───────────┤
  │ Pushed in last 365 days     │ 54,327 │ 87.8%     │
  └─────────────────────────────┴────────┴───────────┘
      So about ~30% are actively maintained. That's a pretty big portion of the community.

      However, the new protocol is wire-incompatible in both directions. This means that many of the servers/clients will need to be refactored (not enough to just update the SDK). It will take time and it will be messy (despite SSE deprecation, there are still many servers and clients that are SSE-only). Honestly, a legitimate opportunity for MCP gateways (ours included) to become more valuable by becoming an interoperability layer between protocol incompatible servers/clients.

  • btbuilderan hour ago
    Excellent improvement. The server-side complexity required to handle sessions has been a large burden both on infrastructure and on educating teams on its characteristics.
  • ilc2 hours ago
    I'd made the shift to HTTP/Stateless from MCP a few months ago. It's the right thing to do IMHO. Reliability up, problems down. TOON support is natural, if desired, etc.

    My only question is how do you handle channels in the architecture now. From what I saw in Claude Code, shifting to a totally http world has some timeout issues if a server drops out and comes back. Because of that I'm stuck writing stubs for my internal use MCP, this is fine for me, but if you are cleaning up semantics: Understanding how we expect clients to act around failure would really help, the story.

  • dend3 hours ago
    Hey folks - one of the Lead Maintainers for MCP. Happy that we got this release out the door today, this is an exciting change for those that wanted to roll out remove MCP servers into serverless hosts. There is, of course, more good stuff packed, so if you have questions or feedback - our team is here to help!
    • jakobgman hour ago
      Congrats at shipping the new specification!

      Any new to share on file upload support? We have shipped a MCP server and it has been really frustrating to observe MCP clients fumbling around with base64-encodings, polluting their context window with binary data. SEP-1306 (Binary Mode Elicitation) was superseded by SEP-2356 (File input support for tools and elicitation), and that was in turn superseded by SEP-2631 (File Objects and Transfer) which is currently left in a draft state with little activity.

      Allowing LLM-based agents to shuffle binary data around efficiently and reliably seems like a pretty big gap in the current specification, if you ask me!

      • colinator34 minutes ago
        I concur. Most of my MCP pain is dealing with client's differing ability to handle images. Some clients (old codex) would even truncate the base64 data regardless of how it was json-wrapped. And sometimes they just ingest the base64 date directly into their context window. Not sure if this is an MCP thing or a clients-poorly-implementing-MCP thing.
    • checker3 hours ago
      Thank you for your work! I was looking forward to the stateless update.
    • dan-kwiat2 hours ago
      Great work! Any word on when to expect support across claude clients?
    • cidd2 hours ago
      When will java sdk come out with latest changes from spec?
    • ihsw2 hours ago
      [dead]
    • Oras2 hours ago
      Thank you!

      What’s the best practice for tools where the upstream API only supports basic auth (username/password) and there’s no OBO option? In my case the login returns a token that’s only valid for an hour, so the user has to re-auth after that. Do you stash the credentials on the MCP server and silently refresh, or is there a nicer pattern people are using?

      • dan-kwiat2 hours ago
        URL Elicitation works well if a human is driving the client. Unfortunately MCP client support is patchy but I expect that will change now the protocol is stateless.
  • osinixan hour ago
    This is the right practice. Why put the burden on the server? It is the job of client to remember, not the server. Server is there to serve requests, not do the remembering. That is how http worked from the beginning and that is why it has been successful.
    • progbitsan hour ago
      It was clear from the start (to anyone who ever designed a protocol [1]) that MCP was a pile anti-patterns. They are slowly undoing the mistakes one by one. Maybe next years version will finally be something usable that it could have been from v1.

      [1] https://news.ycombinator.com/item?id=44016783

      • jgilan hour ago
        Yes. However, using something like MCP encourages many companies to claim that they are "integrating AI" -- and typical MCP implementations burn tokens quite profitably.
  • flowofcontrolan hour ago
    The improvements look great. At the same time I wonder if it is possible to keep using MCP 1.x as well for now. Development is expensive, right? It also looks possible to transition to MCP 2.x by tackling the different improvements one at a time as long as we take stateless core first?
    • closetheloopdev27 minutes ago
      I just realized that MCP releases do not use semver. It says this is a 2026-07-28 version which is quite unusual and can be quite hard to keep track of, especially when backwards compatibility is of concerns.

      There is a one-year-old open GitHub issue asking to use semver instead: https://github.com/modelcontextprotocol/modelcontextprotocol...

      • flowofcontrol15 minutes ago
        You are right, in my mind the 2026-07-28 version was MCP 2.0 but the article never mentions that. I do remember having read about MCP 2.0 elsewhere. Regardless, we cannot expect this to be the last impactful change and to me it makes sense to indeed semantically version.
  • hangrybear666an hour ago
    To be honest I've completely ignored this feature and 95% of my colleagues at work have not interacted with it at all - we are not an AI pilled company - but this specification now seems mature enough for me to be excited about developing a server, just haven't found a concrete use case yet that isn't already publicly available.
  • firasd3 hours ago
    Perfect. The actual tool calls are stateless anyway; when an LLM asks get_my_todos and then asks add_todo it’s not actually holding anything in RAM it’s just text going back into the context window (get_my_todos results) and then another tool call

    And even on the server side statefulness is very iffy anyway. How long are you going to hold something in RAM from a client and how long will you hold the connection open

  • varmabudharaju3 hours ago
    are they coming up with an alternative? i use them to monitor workflows that takes days and now i have to make some changes
    • dend3 hours ago
      This protocol change doesn't require you to do anything to existing running MCP code - only if you want to take advantage of new capabilities!
  • djhworld3 hours ago
    Are the HTTP headers for method/name etc even needed at this point and just use urls instead?

    e.g. mymcpserver.com/tools/call?mcp-method=search

  • Lookbefore-org4 minutes ago
    [flagged]
  • pullrun31 minutes ago
    [dead]
  • landver2 hours ago
    [flagged]
  • rupatiwari252 hours ago
    [dead]