Mature RESTful JSON APIs should be easier to boostrap

[d3cline]

We, the industry, already have so so many RESTful JSON APIs, and guess what? We have been building apps with them for decades. In fact the LLMs which we have transitioned to vibe coding with are fully capable of understanding the RESTful API, the bearer token, all of it. But somehow yall have decided that we should re-invent authentication, and abandon RESTful APIs which we have our business logic will full test coverage. My question is pretty simple,
Why are we being forced to re-invent the wheel simply because a company wants to generate hype? To me its purposefully being broken, so much is on purpose being ignored. Why should I be foreced to re-code my entire API, when it would be rather simple to include a configuration for bearer tokens or a simple spec for 'hey its a json server, you send it the data like this' I already have swagger, asking the LLM to go read those docs is just fine.
TLDR to me MCP is classic "Embrace, Extend, Extinguish" Yall are attempting to get us to over extend, trying to disrupt existing business logic of the whole industry. opening up countless security holes.

It should be rather trivial for me to tell the llm how to read the API docs which I have spent a decade building.

[d3cline]

see this image from the official docs, "MCP server C" which is just a JSON wrapper, its clearly something conceptualized by the people behind this, so it should 'just work' and be included as a grandfathered concept. other protocols have backward compatibility. should be pretty easy to understand

[d3cline]

lol, I have 3 of these in prod now, and I stand by my OP. Should be easier. Gave a lightening talk on why it isn't yesterday. The industry doesn't know whats about to hit them tho. Thanks everyone for your work. I have example code here,
https://github.com/d3cline/monerostack
The django-mcp-server package is fantastic and simple way to get 'server c' going, lots of example code out there now.