Chrome DevTools MCP Server

by async23 Your server? Claim it

local only

Chrome DevTools MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 44 installs a week from npm. Last commit 18 Jul 2026.

MCP server for Chrome DevTools

Installs per day peak 168 · avg 15 · -33% w/w

a month agotoday

Installs / week

npm · @async23/chrome-devtools-mcp

Stars

3 open issues

18 Jul 2026

Last commit

0 releases in 90 days

Apache-2.0

License

TypeScript

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command src/daemon/client.ts:123, src/utils/check-for-updates.ts:85

  const child = spawn(process.execPath, [DAEMON_SCRIPT_PATH, ...mcpArgs], {

Builds a file path from a variable src/daemon/utils.ts:35, src/telemetry/persistence.ts:28

    return path.join('\\\\.\\pipe', appName, 'server.sock');

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add chrome-devtools-mcp -- npx -y @async23/chrome-devtools-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.chrome-devtools-mcp]
command = "npx"
args = ["-y", "@async23/chrome-devtools-mcp"]

.cursor/mcp.json

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

.vscode/mcp.json

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

Alternatives to Chrome DevTools MCP

same job, measured the same way

Chrome DevTools MCP

by chromedevtools

MCP server for Chrome DevTools

1 465 302 installs/wk local only

Chrome DevTools MCP

by dinesh-nalla-se

MCP server for Chrome DevTools

32 installs/wk local only

Browser

by cherchyk

MCP server for loading authenticated web pages using Chrome DevTools Protocol

local only

Selenium MCP

by pshivapr

Selenium Tools for MCP

42 installs/wk local only

Safari DevTools MCP

by hayodev

MCP server for Safari DevTools — browser debugging and automation for AI coding agents

43 installs/wk local only

MCP Server Browser

by bytedance

MCP server for browser use access

1 419 installs/wk local only

Real Browser

by ofershap

MCP server + Chrome extension for AI browser control with real sessions.

70 installs/wk local only

Familiar MCP

by dominion525

MCP server that drives the user's real macOS Chrome via AppleScript. 32 tools.

21 installs/wk local only

Chrome DevTools MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Chrome DevTools MCP?

Chrome DevTools MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @async23/chrome-devtools-mcp was installed 44 times last week.

How do I connect Chrome DevTools MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @async23/chrome-devtools-mcp straight from npm; nothing to host, nothing to sign up for.

How many people use Chrome DevTools MCP?

The npm package @async23/chrome-devtools-mcp was installed 44 times in the last week. Week over week that is -33%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Chrome DevTools MCP open source?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 0 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.