WebUplink vs Browser Use
A side-by-side look at the WebUplink and Browser Use MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose WebUplink for browser automation work as a local process; choose Browser Use for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose WebUplink when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WEBUPLINK_API_KEY, WEBUPLINK_BASE_URL, PORT, MCP_HTTP_HOST, MCP_HTTP_ALLOWED_HOSTS. - You want tools like
browse, close_session.
Choose Browser Use when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 49/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | WEBUPLINK_API_KEYWEBUPLINK_BASE_URLPORTMCP_HTTP_HOSTMCP_HTTP_ALLOWED_HOSTS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 118,983 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View WebUplink | View Browser Use |
Tools & capabilities
WebUplink tools 2
browseBrowse a web page or execute tools on a page.close_sessionClose a browser session to free resources.
Browser Use tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WebUplink
{
"mcpServers": {
"webuplink": {
"command": "npx",
"args": [
"--yes",
"--package",
"@webuplink/mcp",
"webuplink-mcp-http"
],
"env": {
"WEBUPLINK_API_KEY": "YOUR_WEBUPLINK_API_KEY_HERE",
"WEBUPLINK_BASE_URL": "YOUR_WEBUPLINK_BASE_URL_HERE",
"PORT": "YOUR_PORT_HERE",
"MCP_HTTP_HOST": "YOUR_MCP_HTTP_HOST_HERE",
"MCP_HTTP_ALLOWED_HOSTS": "YOUR_MCP_HTTP_ALLOWED_HOSTS_HERE"
}
}
}
}
Browser Use
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": [
"browser-use"
]
}
}
}
Frequently asked questions
WebUplink is categorized under Browser Automation and uses a local stdio subprocess. Browser Use belongs to Browser Automation and uses a local stdio subprocess. Pick WebUplink for browser automation work and Browser Use for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
WebUplink has no declared pricing — check the project's own site. Browser Use has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add webuplink and browser-use as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WebUplink has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Browser Use has 45/100 (Fair) with 2 views, 0 installs and 118,983 GitHub stars.
