This is nice! I was thinking of writing something like this myself. One thing I ran into though is that Claude Desktop can't connect to the server-everything with the command you listed. This is in the server logs:
2025-03-11T16:29:00.168Z [@modelcontextprotocol/server-everything] [info] Client transport closed
› Error: Nonexistent flag: --tools echo,add
› See more help with --help
USAGE
$ god run [-t <value>]
FLAGS
-t, --tools=<value> Comma separated list of approved tools
Also, there's no logs for ~/mcpgod for me (that folder doesn't even exist)
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 outside of sandbox), or network calls based on configurable criteria
This is nice! I was thinking of writing something like this myself. One thing I ran into though is that Claude Desktop can't connect to the server-everything with the command you listed. This is in the server logs:
Also, there's no logs for ~/mcpgod for me (that folder doesn't even exist)Thanks!!
Hrm, re that error: What does “god --version” say?
The log might not show up until you get a successful connection. I’ll look into that.
Thanks for trying it out!
I removed the original config and ran the following:
Same error and log occuredI’ve made the mistake of typing “--tools echo” before instead of “--tools=echo”, just in case that was your error too.
What a polite way to point out that their error was a typo.
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 outside of sandbox), or network calls based on configurable criteria
- An UI for tracking of calls
Awesome feedback. I’ll think through this.
The sandbox is spot on; Control what the server can do. Especially important when running locally