← Back to context

Comment by CharlieDigital

4 days ago

"MCP" is the new "API" (MCP over streaming HTTP, after all, is just an API with a structured payload wrapper and defined interactions).

It is only going to continue to proliferate in usage and adoption.

11 comments

CharlieDigital

Reply
Eldodi  4 days ago

With the v2 spec, MCP became a lot closer to APIs by becoming stateless. And there is now a push to use HTTP verbs more extensively to improve caching even better in v3. MCP is converging into APIs but wit great auth and auditing

  • Zambyte  4 days ago

    ... Are both of you using "API" as a synonym for "REST"?

    • imtringued  4 days ago

      This is the worst moment in time to talk about "REST".

      Do you mean the Roy Fielding "REST" or the HTTP API "REST"?

      Calling the latter "REST" is wrong. It's like calling a hermit crab a snail.

      Edit: I forgot to mention, the former is gaining relevance as the elusive evolvable clients are now a thing.

      2 replies →

    • jazzypants  4 days ago

      It's annoying, but that's been pretty common for the last decade. It's just like how everyone uses "REST" to mean "JSON RPC". In the end, we all basically know what the other ones are talking about, so it's pretty pointless to get bogged down in semantics.

      1 reply →