Chrome Devtools MCP vs WebUplink
A side-by-side look at the Chrome Devtools MCP and WebUplink MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chrome Devtools MCP for browser automation work as a local process; choose WebUplink 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 Chrome Devtools MCP 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.
- You want tools like
click, drag, fill.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 65/100 · Great | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | WEBUPLINK_API_KEYWEBUPLINK_BASE_URLPORTMCP_HTTP_HOSTMCP_HTTP_ALLOWED_HOSTS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 54,046 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 56 | 2 |
| Full listing | View Chrome Devtools MCP | View WebUplink |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
WebUplink tools 2
browseBrowse a web page or execute tools on a page.close_sessionClose a browser session to free resources.
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.
Chrome Devtools MCP
{
"mcpServers": {
"chrome-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. WebUplink belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome Devtools MCP for browser automation work and WebUplink 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.
Chrome Devtools MCP is listed as free. Auth: no auth required. WebUplink has no declared pricing — check the project's own site. 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 chrome-devtools-mcp and webuplink as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chrome Devtools MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 54,046 GitHub stars. WebUplink has 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
