What is the key difference between WebRun Browser Automation and Uplink?

WebRun Browser Automation belongs to the Developer Tools category with cloud HTTP/SSE execution, while Uplink belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install WebRun Browser Automation or Uplink in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are WebRun Browser Automation and Uplink free or paid?

WebRun Browser Automation operates under a Free / Open Source model (No auth required). Uplink operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

WebRun Browser Automation lists 0 tools with 0 views and 0 GitHub stars. Uplink lists 0 tools with 0 views and 0 GitHub stars.

Can I use both WebRun Browser Automation and Uplink together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install WebRun Browser Automation or Uplink in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are WebRun Browser Automation and Uplink free to use, or do they require API keys?

WebRun Browser Automation is listed under a Free / Open Source model with No auth required . Uplink operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both WebRun Browser Automation and Uplink at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both webrun-browser-automation and uplink as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, WebRun Browser Automation has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Uplink holds a Quality Score of 30 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

WebRun Browser Automation vs Uplink

In-depth architectural comparison of the WebRun Browser Automation 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.

At a Glance & Executive Verdict

WebRun Browser Automation

Developer Tools · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Uplink

Developer Tools · Remote HTTP/SSE

Quality: 30/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose WebRun Browser Automation if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Uplink if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose WebRun Browser Automation when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore WebRun Browser Automation Details

Choose Uplink when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Uplink Details

Feature & Specification Comparison

Specification	W WebRun Browser Automation Developer Tools	U Uplink Developer Tools
Summary	Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.	Pair a real phone or laptop and run agentic automation in its live, logged-in browser session.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

WebRun Browser Automation Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Uplink Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

WebRun Browser Automation Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "webrun-browser-automation": {
      "url": "https://webrun.ai"
    }
  }
}

Uplink Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "uplink": {
      "url": "https://docs.uplink.build"
    }
  }
}

Frequently Asked Questions

WebRun Browser Automation is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Uplink belongs to Developer Tools using remote streaming HTTP/SSE transport. Select WebRun Browser Automation when you need capabilities focused on developer tools and Uplink when you require tools for developer tools.

More alternatives to WebRun Browser Automation More alternatives to Uplink Developer Tools category hub Canonical compare URL