| >This effect is _significantly_ stronger than putting info about available API/cli into CLAUDE.md. No it's not. Honestly this conversation is extremely weird to me because somehow people are gravely misunderstanding what MCP even purports to do, let alone what it actually CAN do in the most ideal situation. It is a protocol and while the merits of that protocol is certainly under active discussion it's irrelevant because you keep adding qualities about the protocol that it cannot deliver on. Just same facts to help steer this conversation correctly, and maybe help your understanding on what is actually going: * All LLM's/major models have function & tool calling built in. * Your LLMs/models do not have any knowledge on MCP, nor have they been trained on it. * MCP exists, at least the claim, is to help standardize the LIFECYCLE of the tool call. * MCP does not augment or enhance the ability of LLM's in any form. * MCP does not allow you to extend agents. That's an implicit feature. * If you have access to "X" (using your example), you don't need anything that obeys the MCP standard. MCP at best is for developers and tool developers. Your model does not need an MCP server or client or anything else MCP related to do what is already been trained to do. >I would personally prefer some other method but having a way to make agents extensible is extremely useful. They already are. MCP does not help with this. |