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