Mcp is definitely not stateless. It’s explicitly stateful…
See the 2nd bullet where it says “stateful connections” [1]
And I was saying that with OpenAPI, you need a client per API, or at least a series of http api calls.
1. https://spec.modelcontextprotocol.io/specification/2025-03-2...
But HOW is it stateful? That "mandate" the only occurence of that string "state" in that document.
> Higher in what way?
Higher as in at a higher level in the network stack (not exactly, I don’t think, but lower on the same level)
Higher as in you can implement MCP on top of grpc.
You can’t implement grpc in mcp, that doesn’t make sense, because grpc is at a lower level, so to speak, in the network stack.
It’s not a “mandate” it’s a specification for how the protocol works. If the connection isn’t stateful, then it isn’t adhering to the specification.
I mean also like… how is it stateless? For both example transports (stdio and SSE) a connection must be maintained.
ANY connection must be initialized via an MCP message and both server and client must negotiate capabilities.
Those capabilities must be honored through the entire lifetime of the connection.
That alone is state.
I suggest you read the spec…
Mcp is definitely not stateless. It’s explicitly stateful…
See the 2nd bullet where it says “stateful connections” [1]
And I was saying that with OpenAPI, you need a client per API, or at least a series of http api calls.
1. https://spec.modelcontextprotocol.io/specification/2025-03-2...