Re:MCP Is Dead; Long Live MCP
by superturkey650 on Sunday March 15, 2026 @11:46AM
(#47388537)
But the agent harness is still handling the session token for you either way. MCP might be an easy way for agent harness creators to abstract the issue away, but I don’t want to lose all REST conventions just to make it a little easier for them to write an agent harness.
It makes it harder for the LLM to understand what’s going on, not easier.
Re:MCP Is Dead; Long Live MCP
by avereveard on Sunday March 15, 2026 @03:27PM
(#47390966)
again, not all services are rest or with nice api, if they were, you'd just have the agent write scripts.
Re:MCP Is Dead; Long Live MCP
by superturkey650 on Sunday March 15, 2026 @05:27PM
(#47392134)
No, but MCPs aren’t free to build either. So if you need to build an API on top, why would you build an MCP instead of using one of the existing standards that both LLMs and humans already know how to work with?
It makes it part of the protocol so the llm doesn't have to handle it, which is brittle
And look at the patent post I've replied to choice of protocol, I'd like to see a session token over ftp where you need to track the current folder per conversation.