They can certainly build ad-hoc tool chains very easily. But where MCP is valuable is as a means to provide them tested and secure ways of executing more comple

They can certainly build ad-hoc tool chains very easily. But where MCP is valuable is as a means to provide them tested and secure ways of executing more complex workflows, especially if it means you can more easily whitelist actions you otherwise would want to manually approve and where simple pattern matching is insufficient to sanitise the command line. Just having the MCP tool to do something also often seems to encourage at least Claude to aggressively use it. E.g. I added a linter tool to my own experimentaling coding assistant, and I didn't even have to tell Claude to use it - it just started using it after most changes.