Chrome DevTools MCP vs WebLoom
A side-by-side look at the Chrome DevTools MCP and WebLoom 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 WebLoom for browser automation. 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.
- You have the keys it needs:
CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS, CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS. - You want tools like
click, drag, fill.
Choose WebLoom when
- You need dedicated capabilities in the Browser Automation domain.
- You want tools like
navigate, read_tab, screenshot.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 53/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICSCHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 51 | 31 |
| Full listing | View Chrome DevTools MCP | View WebLoom |
Tools & capabilities
Chrome DevTools MCP tools 51
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +39 more on the listing page
WebLoom tools 31
navigateread_tabscreenshotwait_forscroll_tablist_tabsnew_tabclickclick_at_coordsreact_invoke_handlerfillreact_force_change- +19 more on 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.
Chrome DevTools MCP
{
"mcpServers": {
"chrome-devtools-mcp-2": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
],
"env": {
"CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS": "YOUR_CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS_HERE",
"CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS": "YOUR_CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS_HERE"
}
}
}
}
WebLoom
No confirmed install command for WebLoom yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Chrome DevTools MCP is categorized under Browser Automation and uses a local stdio subprocess. WebLoom belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Chrome DevTools MCP for browser automation work and WebLoom 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. WebLoom has no confirmed install command yet — follow its own setup instructions.
Chrome DevTools MCP has no declared pricing — check the project's own site. WebLoom 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-2 and webloom 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 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. WebLoom has 45/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.