Chrome DevTools MCP

What it does

Drives a live Chrome instance over the DevTools protocol: performance traces, network requests, console output, and accessibility snapshots. It answers the question an agent normally cannot — why is this page slow — without a human exporting a profile. Best paired with a local dev server you are already running.

Install

npx -y chrome-devtools-mcp@latest

Client configuration

Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.

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

When to use it

Reach for this when the task needs browser inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.

Other TypeScript servers

• Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
• Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
• Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude