Chrome DevTools MCP (Google)
Last tested 2026-10-22
Score 100/100 · Last tested 2026-10-22 · Version tested 1.11.0 · Package chrome-devtools-mcp · Repo ChromeDevTools/chrome-devtools-mcp
Summary: Chrome DevTools MCP (Google) completed an MCP handshake without credentials and exposed 32 tools.
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install chrome-devtools-mcp (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 32 tools listed in 17.9s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 53,964 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Schema context cost: ~6,048 tokens for 32 tools (27,442 bytes) · about 74% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): medium.
| Model | Quantization | Runs | Task completed | Correct tool | Avg rounds |
|---|---|---|---|---|---|
| qwen2.5-3b-instruct-q4km | Q4_K_M GGUF (bartowski/Qwen2.5-3B-Instruct-GGUF), CPU-only | 3 | 33% | 100% | 4.7 |
| qwen2.5-1.5b-instruct-q4km | Q4_K_M GGUF (bartowski/Qwen2.5-1.5B-Instruct-GGUF), CPU-only | 3 | 0% | 100% | 2 |
Functional tasks (2/2 passed, tested 2026-10-22)
| Task | Tool | Result | Evidence |
|---|---|---|---|
| navigate to https://example.com/ | new_page | pass | [{"type":"text","text":"## Pages\n1: about:blank\n2: Example Domain (https://example.com/) [selected]"}] |
| read page title (expect "Example Domain") | new_page | pass | [{"type":"text","text":"## Pages\n1: about:blank\n2: Example Domain (https://example.com/) [selected]"}] |
Not tested
We did not test behavior with real credentials, security, or performance under load. These are planned; see methodology.
Tools listed
click, close_page, drag, emulate, evaluate_script, fill, fill_form, get_console_message, get_css_styles, get_network_request, handle_dialog, hover, lighthouse_audit, list_console_messages, list_network_requests, list_pages, navigate_page, new_page, performance_analyze_insight, performance_start_trace, performance_stop_trace, press_key, resize_page, screencast_start, screencast_stop, select_page, take_heapsnapshot, take_screenshot, take_snapshot, type_text, upload_file, wait_for
Config used in our test
{
"mcpServers": {
"chrome-devtools-mcp-google": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}FAQ
Is Chrome DevTools MCP (Google) deprecated?
No. chrome-devtools-mcp was not deprecated or archived when we last tested it on 2026-10-22.
What replaces Chrome DevTools MCP (Google)?
Nothing; Chrome DevTools MCP (Google) is not deprecated as of 2026-10-22.
Does Chrome DevTools MCP (Google) need an API key?
No. It completed an MCP handshake with no credentials and listed 32 tools.
Embed the badge
The badge always shows the current score; payment never changes it.