Exactly. and even if so, how are you going to safe guard tool access?
Imagine your favorite email provider has a CLI for reading and sending email - you're cool with the agent reading, but not sending. What are you going to do? Make 2 API keys? Make N API keys for each possible tool configuration you care about?
MCPs make this problem simple and easy to solve. CLIs don't.
I don't think OpenClaw will last that long without security solved well - and MCPs seem to be obvious solution, but actively rejected by that community.
The Skills I have for Claude are all based on personal preferences and reflects the setup I have going. It's a way to narrow the probability space to the specific set which works really well for me.
i've a simple setup with Claude Code and MCPs; and i get real benefits from better task mgmt, email mgmt, calendar, health/food/fitness tracking, working together with claude on tasks (that go into md files).
i don't think we need ClawdBot, but we do need a way to easily interact with the model such that it can create long term memories (likely as files).
Lutra is a native code-mode AI agent that: (a) converts all tools into functions available in a coding environment, (b) uses LLMs to produce code that orchestrates across those tools, (c) has a custom stateless code interpreter to make it all work securely and well.
There's an agent monitor which intercepts requests either using a LLM proxy or hooks, that gives you full telemetry into the agents + MCPs used. And a MCP gateway that enables centralized deployment and securing of MCP.
I've been hoping that Claude Code on the Web also works with MCPs; so I can start getting it to do things beyond just coding. It's pretty awesome to use Git as a source of memory/tracking what's going on and pull requests as a way to build in a human-in-the-loop review flow.