Main
Treat MCPProxy like an “MCP firewall”:
- Keep a curated upstream list and disable anything you don’t use.
- Use
mcpproxy tools list --server=NAMEto validate what tools an upstream actually exposes before trusting it. - Turn on Docker isolation for risky stdio servers so they can’t touch your host filesystem by default.
- Use
doctorand upstream logs during incidents—debugging is faster when the proxy is the single chokepoint.
This is especially useful when you share MCP setups across multiple clients and machines.
FAQ
Q: Is it only a GUI?
A: No. The README includes a full CLI (mcpproxy ...) plus an optional tray UI.
Q: Where is configuration stored?
A: The README shows ~/.mcpproxy/mcp_config.json as the minimal config path.
Q: Does it help with safety? A: Yes. The README describes quarantine and Docker isolation modes for upstream servers.