← All IntelClip / OtherMCP's core problem: mandatory stateful connections
From Did Anthropic finally fix MCP? · ≈0:19
“And I just didn't find myself using it a whole lot in my day-to-day workflows.”
“In fact, I've actually found it more annoying recently because tools like Codeex use it properly.”
“It got so bad that a lot of the MCP stuff that we use was just hosted locally because the amount of infrastructure it would take to host it in the cloud just wasn't worth it when it wasn't being used 99% of the time.”
What’s in it
- Explains why MCP's dedicated-connection design wastes real infrastructure
- Reveals why tools like Codex end up bloating resource use
- Shows why teams quietly moved MCP servers back to local hosting
Clip transcript
caused as many problems as it solved. And I just didn't find myself using it a whole lot in my day-to-day workflows. In fact, I've actually found it more annoying recently because tools like Codeex use it properly. And by using it properly, they end up wasting a bunch of resources because every single MCP server needs to be a dedicated server with a dedicated connection to the client while it's existing. Even if the client never ends up calling it, it has to be bound to a real connection on a real server. It got so bad that a lot of the MCP stuff that we use was just hosted locally because the amount of infrastructure it would take to host it in the cloud just wasn't worth it when it wasn't being used 99% of the time.
Comments
Checking sign-in…
Loading comments…