I have seen a few of these tools and yet to see usefulness further than not having to edit config manually for each client. Wishlist for something I would use: - Always run MCP in a sandbox - If I am gonna browse open source MCP and try them out casually, I need to control permission better than approving tool calling blindly. I prefer to auto approve all calls but control permission for directory access (if run outs…
most of the MCP tools use Python env (uvx) or Node or even Java to run ANY CODE on your machine, so even the python virtual env is a sandbox but it's to isolate the dependencies not the file/network access. If you are unlucky, you can still install a malware mcp server to clean up your disk or send your photos to somewhere. MCP servers are just local scripts. There are some permission control from deno but this is no…
That's not what a sandbox means. PATH enhancement for dependency management is... dependency management, has nothing for security.
> Too many ways to run scripts.
Which is why you need a tool, and not "just" run MCP. Not that hard to run in docker and configure volume mount/ports though.