Re:Stateless MCP has recaptured my interest
by hchja on Wednesday August 05, 2026 @12:48AM
(#49178679)
MCP 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.
Re:Stateless MCP has recaptured my interest
by spike021 on Wednesday August 05, 2026 @01:33AM
(#49178933)
How well does that work in enterprise setups?
Re:Stateless MCP has recaptured my interest
by charcircuit on Wednesday August 05, 2026 @01:38AM
(#49178960)
Well assuming a browser is able to access whatever enterprise thing, the LLM can emulate being one using apps like curl.
Re:Stateless MCP has recaptured my interest
by rixed on Wednesday August 05, 2026 @02:52AM
(#49179423)
why is MCP a pain in Macos?
Re:Stateless MCP has recaptured my interest
by CharlieDigital on Friday August 07, 2026 @10:50AM
(#49211363)
It 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.
Re:Stateless MCP has recaptured my interest
by CharlieDigital on Friday August 07, 2026 @10:51AM
(#49211388)
MCP is even more important now in enterprise and thus the shift towards the streamable, stateless HTTP server implementation.
Wrote about this back in March: https://chrlschn.dev/blog/2026/03/mcp-is-dead-long-live-mcp/
MCP is going to be a foundational piece of enterprise agent infra.