McpProxy vs Uplink

In-depth architectural comparison of the McpProxy and Uplink 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.

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.

Explore McpProxy Details

Choose Uplink when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (Free / Open Source).
• Primary tools included: Live browser automation on a paired device, Reuse of an existing logged-in browser session, DOM, network, and console observation.

Feature & Specification Comparison

Specification	McpProxy jetbrains Browser Automation	Uplink Browser Automation
Summary	A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio	Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "jetbrains-mcpproxy": {
      "command": "npx",
      "args": [
        "-y",
        "executable"
      ],
      "env": {
        "IDE_PORT": "YOUR_IDE_PORT_HERE",
        "HOST": "YOUR_HOST_HERE",
        "LOG_ENABLED": "YOUR_LOG_ENABLED_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "uplink-2": {
      "command": "npx",
      "args": [
        "-y",
        "@uplink-code/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons