Earlier quoted context omitted.
I just view it as a relative minor convenience, but it's not some game-changer IMO. The tool use / function calling thing far predates Anthropic releasing the MCP specification and it really wasn't that onerous to do before either. You could provide a json schema spec and tell the model to generate compliant json to pass to the API in question. MCP doesn't inherently solve any of the problems that come up in that sor…
It seems the benefit of MCP is for Anthropic to enlist the community in building integrations for Claude desktop, no? And if other vendors sign on to support MCP, then it becomes a self reinforcing cycle of adoption.
This is exactly what's happening now. A good portion of applications, frameworks and actors are starting to support it.
I've been reluctant on adopting MCP in applications until there was enough adoption.
However, depending on your use case it may also be too complex for your use case.