←back to thread

MCP is eating the world

(www.stainless.com)
335 points emschwartz | 1 comments | | HN request time: 0s | source
Show context
Animats ◴[] No.44368767[source]
> At Stainless, we’re betting it’s here to stay.

By a seller of MCP.

The trouble with MCP is that it requires a trip through an LLM for every transaction. It's not like the ends negotiate a simple protocol so that later queries are cheap. That's a huge cost increase as traffic increases.

replies(3): >>44369217 #>>44371911 #>>44378534 #
1. bas_sen ◴[] No.44378534[source]
You're right that per-request LLM inference is costly, especially at scale. But I think the bet with MCP (Model Coordinated Protocol) isn’t that every interaction will always hit the LLM, it’s that the LLM bootstraps flexible protocol negotiation, and then clients can cache or formalize the result.

Think of it more like a just-in-time protocol generator. The LLM defines how to talk, once, and the rest of the interaction can be optimized. Expensive at first, but potentially cheaper than baking in rigid APIs for every use case.

Still, lots of unknowns, especially around latency, consistency, and cost.