MCP server
Chrome DevTools MCP Server
- Maintainer
- Official · Google
- Runs
- Local (stdio)
- GitHub
- ★ 54,089, last push 2026-10-24 (checked 2026-10-24)
- License
- Apache-2.0
- Registry
- io.github.ChromeDevTools/chrome-devtools-mcp
- Connects to
- Chrome
Install the Chrome DevTools MCP Server
Pick your client. Each tab starts the same local command. Config shapes checked against each client's docs on 2026-10-25.
Run in a terminal. Everything after -- is the command that starts the server. docs
claude mcp add --transport stdio chrome-devtools -- npx -y chrome-devtools-mcp@latest
Claude Desktop only: Settings > Developer > Edit Config opens claude_desktop_config.json. Add this, save and restart the app. docs
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project), or use the install button. docs
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Add to .vscode/mcp.json (note the "servers" key and the type), or use the install button. Command Palette > "MCP: Open User Configuration" for all workspaces. docs
{
"servers": {
"chrome-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Run codex mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest, or add this to ~/.codex/config.toml. docs
[mcp_servers.chrome-devtools] command = "npx" args = ["-y", "chrome-devtools-mcp@latest"]
Run in a terminal (-s user adds it for all projects; the default is this project). docs
gemini mcp add -s user chrome-devtools npx -- -y chrome-devtools-mcp@latest
Run in a terminal; it writes ~/.copilot/mcp-config.json. docs
copilot mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
Add to mcp_config.json: ~/.config/devin/mcp_config.json on macOS and Linux (older installs: ~/.codeium/windsurf/mcp_config.json), %APPDATA%\devin\ on Windows. docs
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Add to Zed's settings.json (or Settings > AI > MCP Servers > Add Server). Remote servers without an Authorization header sign in with OAuth. docs
{
"context_servers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Add to opencode.json in the project (or ~/.config/opencode/opencode.json). docs
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrome-devtools": {
"type": "local",
"command": [
"npx",
"-y",
"chrome-devtools-mcp@latest"
],
"enabled": true
}
}
}Add to ~/.kiro/settings/mcp.json (all projects) or .kiro/settings/mcp.json (this project). docs
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}MCP Servers > Configure > Configure MCP Servers opens cline_mcp_settings.json; add this entry. docs
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}Tools it exposes
Grouped as input and navigation automation, emulation, performance, network, debugging, memory and more. A selection:
navigate_page: Go to a URL, back, forward or reloadtake_snapshot: Text snapshot of the page from the accessibility treeclick: Click an elementfill_form: Fill several form fields at oncetake_screenshot: Screenshot of the page or an elementlist_console_messages: Console messages since the last navigationlist_network_requests: Recent network requestsevaluate_script: Run JavaScript in the pageperformance_start_trace: Record a trace for Core Web Vitals (LCP, INP, CLS)performance_analyze_insight: Details on one performance insightlighthouse_audit: Lighthouse accessibility, SEO and best-practice auditsemulate: Emulate network, CPU, viewport and more
From the project's own tool list, checked 2026-11-07. Tools change between releases; your client lists the current ones after you connect.
Security notes
- It exposes the browser's content to the MCP client, so don't use it while signed in to accounts you don't want the agent to see (README disclaimer).
- Google collects usage statistics by default; opt out with --no-usage-statistics or CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS. Performance tools may send trace URLs to the Google CrUX API.
- The local server runs with your user's permissions (npx downloads it from npm on first run). The package is pinned to @latest, so each start can pull a new version; pin a version if you want to review updates.
- It reads web pages, and a page can carry prompt-injection instructions. Keep approval prompts on and use a browser profile without your personal sign-ins.
Alternatives
- Browser Useofficial · ★ 119k
An agent that drives a real Chrome to finish tasks: fill forms, click through flows, extract data.
- Playwrightofficial · ★ 39k
Browser automation through the accessibility tree: click, type, navigate and snapshot pages, no screenshots needed.
- Skyvernofficial · ★ 23k
AI browser automation in Skyvern's cloud: navigate, fill forms and pull data from any site.
- Apifyofficial · ★ 13k
Run any of thousands of Apify scrapers (Actors) for social media, maps, e-commerce and more.
- Firecrawlofficial · ★ 7.7k
Scrape, crawl, map and search websites into clean Markdown or JSON.
- Bright Dataofficial · ★ 2.7k
Web search and scraping that gets past blocks and CAPTCHAs, with a free monthly quota.
- Hyperbrowserofficial · ★ 791
Scrape, crawl and extract with cloud browsers, plus browser-use and Claude computer-use agents.
- ScrapeGraphAIofficial · ★ 117
Extract structured data from pages with a prompt, plus smart crawling.
Comparing servers for one product? Chrome MCP servers
FAQ
What does the Chrome DevTools MCP Server do?+
Control a live Chrome: performance traces, network requests, console and screenshots for debugging. Its tools include navigate_page, take_snapshot, click, fill_form and take_screenshot.
Is the Chrome DevTools MCP server official?+
Official: built and maintained by Google.
How do I add Chrome DevTools to Claude Code?+
Run: claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest. Add --scope project to share it with your team through .mcp.json.
How do I use the Chrome DevTools MCP server in Cursor or VS Code?+
Open the Cursor or VS Code tab above: it has the mcp.json entry and a one-click install link. Cursor uses the "mcpServers" key; VS Code uses "servers" and needs a type ("stdio").
Does Chrome DevTools work in ChatGPT and claude.ai?+
No: it runs locally over stdio, and ChatGPT and claude.ai only connect to remote servers. Use it in Claude Desktop, Claude Code, Cursor, VS Code or another client that can start a local process.
What are the alternatives to the Chrome DevTools MCP server?+
Other browser & web scraping MCP servers: Browser Use, Playwright, Skyvern, Apify and Firecrawl.