---
slug: "chrome-devtools-mcp"
name: "Chrome DevTools MCP"
effect: "Lets a coding agent control and inspect a live Chrome browser through DevTools"
category: "mcp-server"
tier: "standard"
url: "https://github.com/ChromeDevTools/chrome-devtools-mcp"
github: "ChromeDevTools/chrome-devtools-mcp"
pricing: "open-source"
license: "Apache-2.0"
tags: ["browser", "chrome", "debugging", "performance", "puppeteer"]
platforms: ["any-mcp-client", "claude-code", "codex", "cursor", "gemini-cli", "vscode", "jetbrains", "windsurf"]
install_kind: "mcp-json"
date_added: "2026-10-14"
rank: null
rising_score: 50
stars: 53560
star_velocity: 134.3
velocity_basis: "since creation"
created_at: "2025-09-11T10:39:55Z"
pushed_at: "2026-10-15T04:14:27Z"
signals_status: "ok"
signals_fetched_at: "2026-10-15T05:02:38.599Z"
page: "https://agenttooldrop.com/tools/chrome-devtools-mcp"
---

# Chrome DevTools MCP

Lets a coding agent control and inspect a live Chrome browser through DevTools

Category: MCP servers. Tier: standard (a well-known tool, listed for reference, not ranked). Pricing: Open source. License: Apache-2.0.

Platforms: any-mcp-client, claude-code, codex, cursor, gemini-cli, vscode, jetbrains, windsurf.

## Why you would want it

It gives an agent the parts of Chrome DevTools a developer reaches for: recording performance traces with extracted insights, inspecting network requests, reading console messages with source-mapped stack traces and taking screenshots. Automation runs on Puppeteer and waits for action results automatically. A --slim mode trims the tool set for basic browser tasks, and a separate CLI works without MCP.

## Best for

- Debugging front-end bugs with an agent
- Performance analysis of web pages
- Checking console and network errors after a code change

## Use it when

You want your coding agent to check its changes in a real Chrome instance, reading console, network and performance data the way you would in DevTools.

## Skip it if

You need Firefox or WebKit; only Chrome and Chrome for Testing are officially supported. Usage statistics go to Google by default (opt out with --no-usage-statistics), and performance tools may send trace URLs to the CrUX API unless you pass --no-performance-crux.

## Editor note

The README now titles the project "Chrome DevTools for agents"; the npm package is still chrome-devtools-mcp.

## Install

Add to your MCP client config:

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

Source: https://github.com/ChromeDevTools/chrome-devtools-mcp#readme

## Live signals

Fetched 2026-10-15T05:02:38.599Z (status: ok).

- Repository: ChromeDevTools/chrome-devtools-mcp
- Repository created: 2025-09-11
- Stars: 53,560 (GitHub's count; it cannot be authenticated)
- Stars per day, since repo creation: 134.3 (an average over the repo's life, not a growth rate)
- Forks: 6,625
- Open issues and PRs: 186
- License (GitHub): Apache-2.0
- Last push: 2026-10-15
- Latest release: chrome-devtools-mcp-v1.10.1 (2026-09-23)

## Links

- Website: https://github.com/ChromeDevTools/chrome-devtools-mcp
- GitHub: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Install instructions verified at: https://github.com/ChromeDevTools/chrome-devtools-mcp#readme
- Source for this entry: https://github.com/ChromeDevTools/chrome-devtools-mcp#readme
- AgentToolDrop page: https://agenttooldrop.com/tools/chrome-devtools-mcp
- Full catalog (JSON): https://agenttooldrop.com/tools.json