The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the MCP Log Proxy listing page.
mcp-log-proxy can be used to see the messages to and from a MCP client and a MCP server using a Web interface.
Currently, it only supports the STDIO interface.


All running mcp-log-proxy processes will register themselves in .mcp-log-proxy-instances.json located in your home directory. On the web page, you can use the selector to switch to another proxy instance.
and then
or via Go
mcp-log-proxy requires one argument -command that contains the full command line for starting the MCP server.
For example, to proxy traffic to the melrose-mcp server, the full command is:
This example assumes that both tools are available on your execution PATH.
Once the proxy is started, messages can be viewed on http://localhost:5656.
You can override the HTTP host address (default localhost) using the host flag, for example to listen on all interfaces or a specific interface address:
You can override the Web page title using the title flag:
You can override the HTTP port(default 5656) using the port flag:
When running multiple proxies, the mcp-log-proxy will detect whether a HTTP port is taken and choose a different port instead. Using the Web UI you can select any of the other running proxies.
You can override the log file location of the proxy that captures errors in the proxy itself using the log flag:
This example proxies the use of the melrose-mcp server.
Locate the binaries to get the correct paths.
Proxying the browsermcp server.
This example proxies the use of the melrose-mcp server.
Locate the binaries to get the correct paths.

© 2025, https://ernestmicklei.com. MIT License.