Best for
- Frontend developers who want AI-assisted web debugging and performance analysis
- Scenarios that need browser automation and performance diagnostics in the same tool
C
Chrome DevTools MCP
Official
The Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
GitHub source repository ↗
76FMRS · B
Source and config reviewed
Maintained by the official Chrome DevTools team; tools are organized into input automation, navigation, emulation, performance, and network categories with broad coverage and a dedicated troubleshooting doc. A one-line npx command starts it. This review is a static check of source and docs, not an actual run.
Read the scoring and verification method →Officially maintained by the Google Chrome DevTools team, this MCP server exposes browser input automation, navigation control, device emulation, performance trace analysis, and network request inspection to AI coding assistants — for debugging web issues, analyzing performance bottlenecks, and automating browser actions.
Tools
click
Click a page element
drag
Drag a page element
fill
Fill a single input field
fill_form
Fill multiple form fields at once
handle_dialog
Handle a browser dialog (alert/confirm/prompt)
hover
Hover over a page element
press_key
Simulate a key press
type_text
Type text
upload_file
Upload a file
click_at
Click at specific coordinates
close_page
Close a page
list_pages
List all currently open pages
navigate_page
Navigate a page to a URL
new_page
Open a new page
select_page
Switch to a specific page
wait_for
Wait for a condition to be met
emulate
Emulate a device/network environment
resize_page
Resize the page viewport
performance_analyze_insight
Analyze a specific insight from a performance trace
performance_start_trace
Start recording a performance trace
performance_stop_trace
Stop the performance trace and return results
get_network_request
Get details of a specific network request
Setup
Start via `npx -y chrome-devtools-mcp@latest` — the `@latest` tag ensures you always run the newest version. For basic browser tasks only, add the `--slim` flag for a leaner mode with fewer tools enabled.
claude_desktop_config.json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
Fit and risk
Not for
- Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
Required permissions
- Requires a local Chrome browser instance to run
- navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
Risks and side effects
- Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
- performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
Troubleshooting
- Tools don't respond: confirm Chrome has started correctly and the MCP client has permission to connect
- Performance trace results look off: make sure no other process was competing for system resources during the trace, skewing the data
- Element actions fail: check the common issues listed in docs/troubleshooting.md
Use cases
Have an AI assistant analyze a performance trace to pinpoint what's slowing page load
Automate filling forms and clicking through a web task
Inspect a specific network request's response and timing
Emulate different devices and network conditions to test page adaptation
Supported clients
Claude CodeFull support
VS CodeFull support
CursorFull support
WindsurfFull support
JetBrainsFull support
ClineFull support
AmpFull support
KiroFull support
AntigravityFull support