Back to directory

Chrome DevTools for agents

Chrome DevTools for agents lets a coding agent control and inspect a live Chrome browser through an MCP server, giving it DevTools-level automation, debugging and performance analysis.

Chrome DevTools for agents

It records performance traces and extracts actionable insights, analyzes network requests, takes screenshots, and reads console messages with source-mapped stack traces, automating actions reliably through Puppeteer with automatic waiting for results; a CLI is also available for use without MCP. It officially supports Google Chrome and Chrome for Testing, with other Chromium-based browsers unsupported and best-effort only.

Usage statistics such as tool invocation success rates and latency are collected by default to improve the server, and can be disabled with a startup flag or an environment variable, as can periodic checks against the npm registry for a newer version; some performance tools also send trace URLs to a Google service for real-user field data unless disabled separately.

TypeScript, Apache-2.0.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.