6 ms·
Stateless MCP was already possible before this and made sense for whole classes of use cases where it helps to have a remote fleet of servers. Wrote about this
by CharlieDigital 1mo ago
Stateless MCP was already possible before this and made sense for whole classes of use cases where it helps to have a remote fleet of servers.
Wrote about this back in March: https://chrlschn.dev/blog/2026/03/mcp-is-dead-long-live-mcp/ https://chrlschn.dev/blog/2026/03/mcp-is-dead-long-live-mcp/
MCP is going to be a foundational piece of enterprise agent infra.
- hchja 1mo agoMCP was much more important when agents weren’t able to accurately make tool calls. Nowadays, these agents are more capable and I think you can replace MCP (which is a pain on macOS), with simple CLI tools and expose them to agents via system prompt, skills, or other API documentation.
- spike021 1mo agoHow well does that work in enterprise setups?
- charcircuit 1mo agoWell assuming a browser is able to access whatever enterprise thing, the LLM can emulate being one using apps like curl.
- rixed 1mo agowhy is MCP a pain in Macos?
- CharlieDigital 1mo agoIt isn't. MCP over streamable HTTP is just JSON RPC payload over HTTP. The internal interface for the ChatGPT app and Coded are all MCP based (stdio on local). All enterprise AI rollout is eventually going to converge on MCP as a key piece of that infra because it can mask credentials behind one gateway that's easier to control and more secure.
- CharlieDigital 1mo agoMCP is even more important now in enterprise and thus the shift towards the streamable, stateless HTTP server implementation.