Earlier quoted context omitted.
the maintenance burden is the real MCP killer nobody talks about. ... for dev tooling? just write better CLIs. You realize those custom CLIs you're writing will now need to be maintained too, right?
fair point, but there's a difference between maintaining a CLI you own vs depending on a third party to maintain a wrapper around an API you could call directly. not to mention the mcp protocol is fairly nascent whereas CLIs are much more battle-tested
Which is why you should use official MCP servers, and plenty of products do offer an official MCP server.