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

5 comments

• nbbaier 17 hours ago ago

  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)
  [-]
  • gavinuhma 11 hours ago ago

    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!

    [-]
    • nbbaier 9 hours ago ago

      I removed the original config and ran the following:

        19:28:36 ~ $ npx -y mcpgod --version
        mcpgod/0.0.2 darwin-arm64 node-v23.9.0
      
        19:28:47 ~ $ npx -y mcpgod add @modelcontextprotocol/server-everything --client 
        claude --tools=echo,add
      

      Same error and log occured
    • gavinuhma 11 hours ago ago

      I’ve made the mistake of typing “--tools echo” before instead of “--tools=echo”, just in case that was your error too.

• nsonha 2 hours ago ago

  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