Zenlink MCP vs McpProxy — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Zenlink MCP vs McpProxy
In-depth architectural comparison of the Zenlink MCP and McpProxy MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Zenlink MCP
Browser Automation · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
McpProxy
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Zenlink MCP if you need specialized Browser Automation tools running via a local process. Choose McpProxy if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Zenlink MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: IDE_PORT, HOST, LOG_ENABLED.
Primary tools included: Proxies MCP requests to JetBrains IDEs via local webserver, Supports configuration of IDE host and port, Enables logging via environment variable.
Waits for a CSS selector to appear and become visible on the page. Returns immediately when found rather than sleeping a fixed duration — use this instead of `sleep` when waiting for dynamic/JS-rendered content.
zen_batch
Run multiple commands in one request. Supports all actions including `waitForElement`, `trustedClick`, and `sleep`:
McpProxy Tools (5)
Proxies MCP requests to JetBrains IDEs via local webserver
Supports configuration of IDE host and port
Enables logging via environment variable
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Zenlink MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, McpProxy belongs to Browser Automation using local stdio subprocess. Select Zenlink MCP when you need capabilities focused on browser automation and McpProxy when you require tools for browser automation.