A side-by-side look at the MCP Log Proxy and Nx Console MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Log Proxy for developer tools work as a local process; choose Nx Console for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Log Proxy when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Nx Console tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Log Proxy is categorized under Developer Tools and uses a local stdio subprocess. Nx Console belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Log Proxy for developer tools work and Nx Console for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Log Proxy is listed as free. Auth: no auth required. Nx Console has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add emicklei-mcp-log-proxy and nx-console as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Log Proxy has a quality signal of 47/100 (Fair) with 4 views, 0 installs and 32 GitHub stars. Nx Console has 51/100 (Good) with 2 views, 0 installs and 1,412 GitHub stars.