As far as I can tell MCP is just "we bothered to document our api in a programatically readable way".Just generate CLI tools, with docs, from MCP servers on demand.
It's exactly that, but I don't see the issue. API+Docs under a single URL looks like a win for me. It also warrants a new name.
Exactly! Swagger descriptions+GUI[1], HATEOAS[2], and JSONAPI[3] all coming together in jubilous harmony if MCP pulled its head out of the sand, but instead we get the XKCD#927[4] situation.1: <a href="https://swagger.io/docs/specification/v3_0/adding-examples/" rel="nofollow">https://swagger.io/docs/specification/v3_0/adding-examples/2: <a href="https://en.wikipedia.org/wiki/HATEOAS" rel="nofollow">https://en.wikipedia.org/wiki/HATEOAS3: <a href="https://jsonapi.org" rel="nofollow">https://jsonapi.org4: <a href="https://xkcd.com/927/" rel="nofollow">https://xkcd.com/927/
blamestross · · focus · HN ↗
Just generate CLI tools, with docs, from MCP servers on demand.
tiborsaas · · focus · HN ↗
avereveard · · focus · HN ↗
Swagger was the new old name for the concept
ramses0 · · focus · HN ↗
1: <a href="https://swagger.io/docs/specification/v3_0/adding-examples/" rel="nofollow">https://swagger.io/docs/specification/v3_0/adding-examples/
2: <a href="https://en.wikipedia.org/wiki/HATEOAS" rel="nofollow">https://en.wikipedia.org/wiki/HATEOAS
3: <a href="https://jsonapi.org" rel="nofollow">https://jsonapi.org
4: <a href="https://xkcd.com/927/" rel="nofollow">https://xkcd.com/927/