Show HN: MCPGod: Fine-grained control over MCP clients, servers, and tools

by gavinuhmaon 3/11/25, 12:58 PMwith 11 comments
by nbbaieron 3/11/25, 4:33 PM

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)

by nsonhaon 3/12/25, 7:36 AM

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

by Prosammeron 3/14/25, 4:38 PM

Looks cool! Do you see this as something that should be handled by the MCP spec in the future? I'm surprised this isn't built in already.