It's literally JSON-RPC I'm not sure why you say it's a REST API. It's not even close to a REST API.
replydeleted
replyIn this context/application I see a lot of similarities.
replyThey both provide stateless RPC methods and human readable metadata that makes them easy to route.
You could ask why json-rpc was even necessary for 2.0. I think mostly just for stdio and backwards compatibility.
In the venn diagram of MCP and REST, there is an (optional) overlap for sure but one does not subsume the other.
replyYeah, this feels like one of those ‘explainers’ that feel like they are great to someone who already knows how the system works, but don’t actually work for newbies because they tacitly assume knowledge of the shape of the system that seems ‘obvious’ to someone steeped in it.
replyTo me the writing itself seems pretty economical.
replyFrom your comment, I expected to be annoyed by a bunch of slop or obscurities.
My guess is the writing did not come straight out of an LLM and was carefully curated.
If I’m wrong I’d love to have the style prompt.