MCP Radar
English中文
Active

chrome-devtools-mcp

Chrome DevTools for coding agents

The Chrome DevTools MCP Server hands the browser's developer tools to your AI. When you're debugging a frontend issue, you no longer paste console errors and network-panel screenshots by hand — the AI opens a Chrome and reads the page's real DOM, network requests and console output itself.

For web developers this removes the reproduce-screenshot-describe loop. The AI sees what actually happened in the browser, so it has fuller context for finding the problem.

GitHub ↗npm ↗
84
TrustScore
✅ No clear abandonment signal detected; complete security and compatibility checks before production use

Why use it

Good for: developers who want the AI to help debug frontend issues, analyze page performance, or reproduce browser-only bugs that only appear in a real environment.

Before connecting: it launches a real browser process, so it is heavier than a pure API server. The maintenance signals, TrustScore and derived client compatibility are all below.

Works with these clients

  • Claude Desktopnpx
  • Claude Codenpx
  • Cursornpx
  • VS Codenpx
  • Windsurfnpx

Derived from the registry manifest (package type and transport) — we have not installed it ourselves. Check the official README before relying on it.

Install / Connect

claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcp

Follow the official README; env and args vary per server.

🛠️ Maintenance weight 30% · 100 pts

📝
Last committoday
📈
Commits in 90 days100
💬
Recent issues with replies100%
🗃️
Repo statusNormal

📊 Adoption weight 25% · 94 pts

⭐
GitHub stars49.4k (90d +0%)
📦
npm weekly downloads2211.1k（+0%）
🚀
Releases per month3.7

✅ Usability weight 20% · 55 pts

📋
Official registryNot listed
▶️
Runnable entryResolvable (npx/remote)
🔍
AuditabilityOpen-source repo, auditable

❤️ Health & community weight 25% · 78 pts

🐛
open issues99
🔀
open PRs—
⚖️
LicenseApache-2.0
👥
Contributors / forks30 / 3.4k

Sources: GitHub API · npm registry · updated 2026-08-19

90-day trend

⭐ stars +0%

📦 weekly downloads +0%

Frequently Asked Questions

Does it need Chrome installed locally?

It needs a Chrome/Chromium it can drive. Check the official README for exact version requirements.

Which AI clients are supported?

It's a local stdio server, so Claude Desktop, Claude Code, Cursor and VS Code all work. See the compatibility section below.

Similar / alternative servers

How to choose among these

Browser servers differ mainly on local vs. cloud, and whether you need to handle login / dynamic pages.

  • Operate login-gated, JS-rendered sitesPick Playwright MCP — a real browser with the fullest interaction
  • Bulk-scrape static sites to Markdown / feed a knowledge basePick Firecrawl — easiest for whole-site crawl and extraction
  • Want scaled, cloud-hosted browsersPick Browserbase / Hyperbrowser — cloud sessions

io.github.achiya-automation/safari-mcp

Native Safari browser automation for AI agents — 97 tools, zero Chrome overhead.

80
Automation & Productivity
Active⭐ 165updated 1d ago

io.github.ChromeDevTools/chrome-devtools-mcp

Chrome DevTools MCP

93
Active⭐ 49.4kupdated today

io.github.hongnoul/hwatu

Verification browser for coding agents: headless WebKit, DOM eval, screenshots,

72
Active⭐ 77updated 1d ago

playwriter

Chrome extension & CLI to let agents control your browser. Runs Playwright snipp

70
Active⭐ 3.8kupdated 3d ago

One email a week, 5 minutes to see what happened in the MCP ecosystem

New servers, breakout trends, abandonment alerts — tracked automatically, curated by hand, sent to your inbox.

One email a week · unsubscribe anytime · no data selling