180 karma · joined June 1, 2014
connect at jngiam [at] mintmcp.com
We’re excited about XAA, it will simplify many flows
Love to discuss and see how we can make this more standard
(all pass through)
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.
If you’re vibing and doing the open claw thing without any security concerns; then you’re absolutely right.
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).
We always need something for that - and it needs to work for non tech users too
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.
The LLMs are also really bad at generating correct code for OAuth logic - there are too many conditions there, and the DCR dance is fairly complicated to get right.
Shameless plug: we're building a MCP gateway that takes in any MCP server and we do the heavy lifting to make it compatible with any client on the other end (Claude, ChatGPT - even with custom actions); as a nice bonus it gives you SSO/logs as well. https://mintmcp.com if you're interested.
Pretty cool though! Will need to use it for some more isolated work/code edits. Claude Code is now my workhorse for a ton of stuff including non-coding work (esp. with the right MCPs)
If we're considering primarily coding workflows and CLI-based agents like Claude Code, I think it's true that CLI tools can provide a ton of value. But once we go beyond that to other roles - e.g., CRM work, sales, support, operations, finance; MCP-based tools are going to have a better form factor.
I think Skills go hand-in-hand with MCPs, it's not a competition between the two and they have different purposes.
I am interested though, when the python code in Skills can call MCPs directly via the interpreter... that is the big unlock (something we have tried and found to work really well).
You don’t want to have a blanket policy since that makes it no longer useful, but you want to know when something bad is happening.