McpProxy vs Manzanas — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
McpProxy vs Manzanas
In-depth architectural comparison of the McpProxy and Manzanas 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: 59/100 (Good) | Auth: No auth required
Manzanas
Browser Automation · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose McpProxy if you need specialized Browser Automation tools running via a local process. Choose Manzanas 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.
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: MANZANASD_ADDR.
Primary tools included: TTL-bounded exclusive leases with FIFO queue, Warm pool of SIGSTOPped simulators for fast lease activation, UI actions: tap, type, scroll by accessibility label.
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
Drive iOS simulators from Claude Code, Cursor or Codex by accessibility label instead of screenshot-and-tap-coordinates. Exposes ui_tree, tap_element, type_into_element, wait_for_element and scroll_to_element, and every action reports whether the UI actually changed. A Mac daemon underneath hands out simulators as TTL leases with a queue and keeps a SIGSTOP warm pool, so a lease gets a live simulator in about 0.28s instead of a 7s cold boot, and multiple agents can share one Mac without colliding. Open source, MIT.
Tools & Capabilities Breakdown
McpProxy Tools (5)
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
Manzanas Tools (6)
TTL-bounded exclusive leases with FIFO queue
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, Manzanas belongs to Browser Automation using local stdio subprocess. Select McpProxy when you need capabilities focused on browser automation and Manzanas when you require tools for browser automation.