Re:Stateless MCP has recaptured my interest
by Foobar8568 on Wednesday August 05, 2026 @02:16AM
(#49179197)
I still don't get MCP. Most likely because I didn't really check but the first feeling is creating a problem to solve a problem that doesn't exist in the first place.
[ Parent
| on HN ]
Re:Stateless MCP has recaptured my interest
by mmasu on Wednesday August 05, 2026 @02:19AM
(#49179222)
In enterprise MCP allows users to access resources that could either be unsafe or impractical to consume via API or CLI. It is a powerful pattern, supported by virtually all clients (Cursor, Claude Code, Codex, whatever) and easily implemented in custom harnesses. If you don’t need it you don’t, but it has many useful applications. Stateless will make it a lot more practical to expand applications.
Re:Stateless MCP has recaptured my interest
by cheeze on Wednesday August 05, 2026 @03:52AM
(#49179810)
What is an example of something that is unsafe to consume via API or CLI?
Isn't MCP _an API_?
Re:Stateless MCP has recaptured my interest
by PetahNZ on Wednesday August 05, 2026 @06:20AM
(#49180762)
Its more targeted? Sure I can allow an LLM to access CLI, but then it will try to pipe to other command, write scripts etc. MCP is simply request/response. Its not really that technically different, but the way you and LLMs interact with it allows for easier control. IMHO.
Re:Stateless MCP has recaptured my interest
by progbits on Wednesday August 05, 2026 @06:23AM
(#49180786)
It is.
MCP serves a single purpose: If you ask some company for API support for some stuff you can do via web UI but not API, they might say no for many reasons. But when you ask for MCP, suddenly you trigger AI FOMO and it will be available right away.
Re:Stateless MCP has recaptured my interest
by lexandstuff on Wednesday August 05, 2026 @06:39AM
(#49180905)
Yes, MCP is an API.
Previously, it was an API with a weird stateful standard; now it is essentially a bog-standard stateless JSON-RPC API with conventions for tool discovery, long-running tasks and multi-round-trip requests
If you wrote your own JSON-RPC API for an LLM, you would probably eventually end up with something that looks very much like the standard they're describing.
Re:Stateless MCP has recaptured my interest
by Foobar8568 on Wednesday August 05, 2026 @09:09AM
(#49182372)
Ahh so it's the 2025 name for CORBA? just kidding, I meant SOA /s
But your answer is the first one that seems to be relevant, so thank you.
Re:Stateless MCP has recaptured my interest
by DarkNova6 on Wednesday August 05, 2026 @04:25AM
(#49180043)
I don't get it. I thought the advantage is that you have a client as a library with integrated auth & other tech stuff handled so you can just focus on using the API? Because otherwise you could just use REST with basic endpoint code.
Re:Stateless MCP has recaptured my interest
by qalmakka on Wednesday August 05, 2026 @02:24AM
(#49179245)
It's mostly useful to allow sandboxed AI apps to access external functionality. If an LLM has any kind of access to a CLI then it stops making sense, because LLMs are very good at CLI and almost always they use less tokens doing that. Plus, you human can easily use a cli tool, while mcp is just for agents.
Re:Stateless MCP has recaptured my interest
by bob1029 on Wednesday August 05, 2026 @03:22AM
(#49179615)
MCP is most useful for extending agent loops with external tools. If you are building your own loops from scratch and don't intend to support external tools, MCP doesn't add anything.
Re:Stateless MCP has recaptured my interest
by hahahaa on Wednesday August 05, 2026 @03:00AM
(#49179485)
Well for a non-coding (no CLI tooling) flow it means you don't need a sandbox and it provides a plugin architecture.
Re:Stateless MCP has recaptured my interest
by kmarc on Wednesday August 05, 2026 @02:25AM
(#49179252)
I my mind it's mostly corporate socio-political. Your management have no idea what a (rest) API is, but they saw MCP in countless LinkedIn slop and therefore you are allowed to work on one / use an upstream solution to connect the agents to your 23 year old monolithic unmaintained homebrew CRM that only runs because overcompensated Frank is still willing to pet it manually.