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!

▲

jakobgm 21 minutes ago | parent | next [-]

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 turned 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!

	▲	colinator 3 minutes ago \| parent [-]
		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.

▲

checker 2 hours ago | parent | prev | next [-]

Thank you for your work! I was looking forward to the stateless update.

▲

dan-kwiat 2 hours ago | parent | prev | next [-]

Great work! Any word on when to expect support across claude clients?

	▲	dend an hour ago \| parent [-]
		We are actively working on this - the support is rolling out across the ecosystem: https://claude.com/blog/bringing-mcp-2026-07-28-to-claude

▲

cidd 2 hours ago | parent | prev | next [-]

When will java sdk come out with latest changes from spec?

▲

ihsw an hour ago | parent | prev | next [-]

[dead]

▲

Oras 2 hours ago | parent | prev [-]

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-kwiat 2 hours ago \| parent [-]
		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.