Chrome Devtools MCP vs Browser Use MCP Server
A side-by-side look at the Chrome Devtools MCP and Browser Use MCP Server 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 Browser Use MCP Server for browser automation over a hosted endpoint. 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 Browser Use MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, CHROME_PATH, PATIENT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 65/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | OPENAI_API_KEYCHROME_PATHPATIENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 53,900 | 847 |
| Directory activity | 6 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 56 | Not listed |
| Full listing | View Chrome Devtools MCP | View Browser Use MCP Server |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
Browser Use MCP Server 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.
Chrome Devtools MCP
{
"mcpServers": {
"chrome-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}
Browser Use MCP Server
{
"mcpServers": {
"co-browser-browser-use-mcp-server": {
"url": "http://localhost:8000/sse"
}
}
}
Frequently asked questions
Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. Browser Use MCP Server belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Chrome Devtools MCP for browser automation work and Browser Use MCP Server 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. Browser Use MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 chrome-devtools-mcp and co-browser-browser-use-mcp-server 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 53,900 GitHub stars. Browser Use MCP Server has 55/100 (Good) with 6 views, 0 installs and 847 GitHub stars.
