Skip to content
  1. Home
  2. MCP servers
  3. Chrome DevTools for agents

Chrome DevTools for agents

Lets a coding agent control and inspect a live Chrome via DevTools

What it is

From the Chrome DevTools team: an MCP server (and CLI) that drives Chrome through Puppeteer and exposes DevTools data. An agent can record performance traces, read console messages with source-mapped stacks, inspect network requests and take screenshots. For front-end debugging and performance work.

Good for

  • Record and analyse a performance trace
  • Read console errors and network requests
  • Automate a page flow and screenshot it

Install or run

npx -y chrome-devtools-mcp@latest

Command as given in the project README. Read the repository before you run anything on your machine.

What you need

Node.js LTS; Chrome

Worth knowingUsage statistics are sent to Google by default (opt out with --no-usage-statistics); the agent can read everything in that browser.

Sources

The summary is ours, written from the README. Spotted an error? See how we work.

More for coding

See the topic →
  • REA: Reverse Engineer Anything

    morluto/rea

    MCP server and CLI for agent-driven reverse engineering of apps and binaries

    MCP serverGitHub stars: 456k
  • Context7

    upstash/context7

    Version-specific library docs and code examples fetched into the agent

    MCP serverGitHub stars: 65k
  • GitNexus

    abhigyanpatwari/GitNexus

    Indexes a codebase into a graph of symbols, calls and execution flows

    MCP serverGitHub stars: 48k
  • Context7 plugin

    anthropics/claude-plugins-official

    Current library docs via Context7's hosted MCP server

    MCP serverGitHub stars: 47k