Clip / Other

How stateless MCP simplifies infrastructure

From Did Anthropic finally fix MCP? · ≈6:32

“Each agent can just hit a random endpoint and get back some JSON and then decide when it wants to do things from there instead of it being a bound connection.”

“It is just an endpoint that is hit which is to be frank the way it always should have worked because all MCP should be doing is informing the agent of what its capabilities are and then giving the agent everything it needs in order to call and do things.”

What’s in it

Explains why stateless MCP endpoints beat bound connections
Shows how agents discover capabilities via simple JSON responses
Argues hosting infra can be local or cloud without added complexity

Watch this moment

Clip transcript

looks a little sketchy but now that it's stateless none of that matters. Each agent can just hit a random endpoint and get back some JSON and then decide when it wants to do things from there instead of it being a bound connection. It is just an endpoint that is hit which is to be frank the way it always should have worked because all MCP should be doing is informing the agent of what its capabilities are and then giving the agent everything it needs in order to call and do things. This also means the infrastructure you host it on and the ways you provide it on your computer can be entirely different too. You can have a simple local HTTP API or one in the cloud that fetches data and has like one little key in it to distinguish between things instead of keeping a bound