McpProxy vs Zenlink MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
McpProxy vs Zenlink MCP
In-depth architectural comparison of the McpProxy and Zenlink MCP 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
McpProxy
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Zenlink MCP
Browser Automation · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose McpProxy if you need specialized Browser Automation tools running via a local process. Choose Zenlink MCP 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 McpProxy 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 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.
Proxies MCP requests to JetBrains IDEs via local webserver
Supports configuration of IDE host and port
Enables logging via environment variable
Compatible with VS Code and Claude Desktop MCP clients
Supports external connections with proper IDE settings
Zenlink MCP Tools (2)
zen_wait_for_element
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.
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).
McpProxy is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Zenlink MCP belongs to Browser Automation using local stdio subprocess. Select McpProxy when you need capabilities focused on browser automation and Zenlink MCP when you require tools for browser automation.