MCP is something that's filled with buzzwords and seems like something created solely so that you can be "sold" something. From what I actually gathered, it's basically somehow four things rolled into one:

* A communication protocol, json-rpc esque except it can be done over stdio or via HTTP

* A discovery protocol, like Swagger, to document the "tools" that an endpoint exposes and how it should be used

* A tool calling convention, the specific sequence of tokens the LLM needs to output for something to be recognized as a tool call

* A thin glue layer orchestrating all of the above: injecting the list of available tools into the LLM context, parsing LLM output to detect tool calls and invoke them with appropriate args, and inject results back into LLM context

> * A thin glue layer orchestrating all of the above: injecting the list of available tools into the LLM context, parsing LLM output to detect tool calls and invoke them with appropriate args, and inject results back into LLM context

Yeah llm rules. You think there must be something more to it. There's not.