Chrome DevTools MCP

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. Its 40 documented tools cover heapsnapshot, page, performance, take.

People connecting browser automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-23 · ★ 49,617 · #2 OF 196 MAINTAINED BROWSER AUTOMATION · VERIFIED 2026-08-25

Apache-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Chrome DevTools MCP

Claude Code

claude mcp add chromedevtools-chrome-devtools-mcp -- npx -y chrome-devtools-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "chromedevtools-chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

npm package chrome-devtools-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.ChromeDevTools is GitHub-verified and matches the repo owner

03 · What Chrome DevTools MCP can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

An agent gets 40 documented tools spanning heapsnapshot, page, performance, take, including click, drag, fill, fill_form.

Capability map

Tools grouped from the project's README - what Chrome DevTools MCP lets an agent do.

Heapsnapshot

6 tools - e.g. Get Heapsnapshot Class Nodes; Get Heapsnapshot Details; Get Heapsnapshot Dominators

get_heapsnapshot_class_nodes · get_heapsnapshot_details · get_heapsnapshot_dominators · get_heapsnapshot_duplicate_strings · get_heapsnapshot_edges · get_heapsnapshot_object_details

Performance

3 tools - e.g. Performance Analyze Insight; Performance Start Trace; Performance Stop Trace

performance_analyze_insight · performance_start_trace · performance_stop_trace

Take

3 tools - e.g. Take Screenshot; Take Snapshot; Take Heapsnapshot

take_screenshot · take_snapshot · take_heapsnapshot

Click

2 tools - e.g. Click; Click At

click · click_at

Fill

2 tools - e.g. Fill; Fill Form

fill · fill_form

create & write

2 tools - e.g. Upload File; New Page

upload_file · new_page

Close

2 tools - e.g. Close Page; Close Heapsnapshot

close_page · close_heapsnapshot

Network

2 tools - e.g. Get Network Request; List Network Requests

get_network_request · list_network_requests

Limitations (from the README)

[!WARNING] Enabling the remote debugging port opens up a debugging port on the running browser instance. Any application on your machine can connect to this port and control the browser. Make sure that you are not browsing any sensitive websites while the debugging port is open.

Latest releases

chrome-devtools-mcp-v1.7.0 · 2026-08-10

1.7.0 (2026-08-10) · add a utility function to check for localhost. · Add get_heapsnapshot_object_details MCP tool · Emit native contexts in snapshot summary · Filter heap snapshot objects by native context · log…

chrome-devtools-mcp-v1.6.0 · 2026-07-14

1.6.0 (2026-07-14) · add experimentalGcfFormat flag for GCF-encoded tool responses · Print object count and total sizes in get_heapsnapshot_details · support --allow-unrestricted-paths configuration · Support filter…

chrome-devtools-mcp-v1.5.0 · 2026-07-03

1.5.0 (2026-07-03) · Add get_heapsnapshot_duplicate_strings MCP tool · Add MCP tools for heap snapshot comparison · Fixes · improve error messages to guide AI agents and developers · create PID directory with secure…

04 · Who maintains Chrome DevTools MCP

Chrome DevTools MCP is maintained by chromedevtools. It's the only MCP server we track from this author; the repo dates to Sep 2025.

05 · Facts

category
browser automation - ranked #2 of 196 actively-maintained browser automation servers as of 2026-08-25.
release cadence
7 releases in the last 90 days (latest 2026-08-10)
registry
io.github.ChromeDevTools/chrome-devtools-mcp (active, first published 2025-09-24 · 49 versions)
packages
npm:chrome-devtools-mcp

06 · Chrome DevTools MCP FAQ

Is Chrome DevTools MCP still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-23 and it shipped 7 releases in the last 90 days. We re-verify nightly.

What can Chrome DevTools MCP do?

An agent gets 40 documented tools spanning heapsnapshot, page, performance, take, including click, drag, fill, fill_form.

How do I install Chrome DevTools MCP?

Run `npx -y chrome-devtools-mcp`. You can also paste the ready-made client config above.

Does Chrome DevTools MCP run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Chrome DevTools MCP

head to head · Chrome DevTools MCP vs Playwright MCP · Agent Device (callstack) vs Chrome DevTools MCP · Chrome DevTools MCP vs Argent

More browser automation MCP servers · Churnkey · SAP ABAP MCP · Mat · CometChat Docs · Crawlio Browser

More TypeScript MCP servers · Fluxmail · Pipedrive CRM · Clari Layer · Clawcall · see all