Chrome DevTools MCP server
The Chrome DevTools team's server for driving and inspecting a live Chrome browser: performance traces, network requests, console messages and Lighthouse audits. Runs locally without authentication.
Local (stdio)No auth
Set up Chrome DevTools MCP
Configuration examples, not tested connections. Replace placeholders and review the upstream documentation before use.
Claude Code
Run in your terminal.
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
Cursor
Merge into ~/.cursor/mcp.json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Codex
Run in your terminal.
codex mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
Gemini CLI
Merge into ~/.gemini/settings.json
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
OpenCode
Merge into ~/.config/opencode/opencode.jsonc
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrome-devtools": {
"type": "local",
"command": [
"npx",
"-y",
"chrome-devtools-mcp@latest"
],
"enabled": true
}
}
}
VS Code
Merge into .vscode/mcp.json
{
"servers": {
"chrome-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Using more than one server?Add to a config with other servers
Step-by-step setup guides: Claude Code and Codex CLI, Cursor and VS Code. In Claude Desktop, the Cursor JSON goes in claude_desktop_config.json. This is a local server that runs on your machine; see remote vs local servers and authentication and security basics.
Overview
Chrome DevTools MCP comes from the Chrome DevTools team and gives a coding agent the same view of a page that a developer gets from DevTools. It is maintained in ChromeDevTools/chrome-devtools-mcp. Version 1.10.1 was released on 23 September 2026, and commits continued into October.
Use it to debug what a change actually does in the browser. navigate_page, click, fill and take_snapshot move through the page. list_network_requests and list_console_messages show failed requests and errors. performance_start_trace, performance_stop_trace and performance_analyze_insight record and explain performance traces, and lighthouse_audit runs a Lighthouse report. take_screenshot and evaluate_script help with checks that the snapshot alone cannot answer.
The server starts with npx -y chrome-devtools-mcp@latest and controls a local Chrome instance. It needs no account. Two defaults are worth knowing before you install it. Google collects usage statistics such as tool success rates and latency; pass --no-usage-statistics to opt out. Performance tools may also send trace URLs to the Chrome UX Report API to fetch real-user data, which --no-performance-crux disables. Because the agent can read anything open in that browser profile, avoid pointing it at sessions you do not want it to see.
Example tools
navigate_pagetake_snapshotlist_network_requestslist_console_messagesperformance_start_tracelighthouse_audit
Tool names are upstream examples. The server's live tool list can differ.
Related Developer Tools servers
Sources
This page was written from the upstream documentation below and last reviewed on 11 October 2026. Listing is not a security or compatibility endorsement. Report a correction through the contact page.