I built MCP Commander to solve a small but growing problem I have: having to repeatedly configure new (and potentially untrustworthy) MCP servers across various tools and projects.
MCP Commander can manage your configuration files across any host application you have that follows the increasingly-standard MCP server configuration file format.
It sits between your MCP hosts and servers to provide visibility to MCP server traffic.
It lets you configure triggers on MCP server traffic, alarming you to things like tool poisoning attempts, authentication hijacking, stealth commands, data exfiltration attempts, etc.
It lets you easily run certain MCP servers inside of Docker. Configure with one click across all your host applications.
I'm hoping to find beta participants to provide feedback. HN participants will receive a free lifetime license in return.
Comments
I built MCP Commander to solve a small but growing problem I have: having to repeatedly configure new (and potentially untrustworthy) MCP servers across various tools and projects.
MCP Commander can manage your configuration files across any host application you have that follows the increasingly-standard MCP server configuration file format.
It sits between your MCP hosts and servers to provide visibility to MCP server traffic.
It lets you configure triggers on MCP server traffic, alarming you to things like tool poisoning attempts, authentication hijacking, stealth commands, data exfiltration attempts, etc.
It lets you easily run certain MCP servers inside of Docker. Configure with one click across all your host applications.
I'm hoping to find beta participants to provide feedback. HN participants will receive a free lifetime license in return.