I think you might be missing the point of this quote, which is that you don't have to introduce additional code into the model to support MCP.

MCP happens at a different layer. You have to run the MCP commands. Or use a client that does it for you:

> But the LLM will never know you are using MCP, unless you are letting it know in the system prompt of tool definitions. You, the developer, is responsible for calling the tools. The LLM only generates a snippet of what tool(s) to call with which input parameters.

The article is describing how MCP works, not making an argument about what it means to "understand" something.

Yeah I think you're right. This is a more likely interpretation: the writer probably isn't actually making a claim regarding understanding.