Chrome DevTools MCP

Official Chrome DevTools MCP server that enables AI coding agents to control and inspect a live Chrome browser. Provides 29 tools across input automation, navigation, emulation, performance analysis, network inspection, and debugging including Lighthouse audits and Chrome DevTools Protocol access.

Evaluated Mar 06, 2026 (0d ago) vunknown
Homepage ↗ Repo ↗ Developer Tools chrome devtools mcp browser-automation debugging lighthouse performance screenshots e2e-testing google
⚙ Agent Friendliness
82
/ 100
Can an agent use this?
🔒 Security
76
/ 100
Is it safe for agents?
⚡ Reliability
76
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
85
Documentation
85
Error Messages
72
Auth Simplicity
88
Rate Limits
75

🔒 Security

TLS Enforcement
88
Auth Strength
72
Scope Granularity
65
Dep. Hygiene
82
Secret Handling
75

No auth for local Chrome DevTools Protocol access. Grants full browser debugging access — security depends on Chrome being local-only. DevTools Protocol can access cookies, localStorage, and network data — high privilege. Use in trusted environments only.

⚡ Reliability

Uptime/SLA
78
Version Stability
78
Breaking Changes
75
Error Recovery
72
AF Security Reliability

Best When

You need AI agents to interact with, debug, or test web applications in a real Chrome browser, especially for development and QA workflows.

Avoid When

You need cross-browser testing, production scraping infrastructure, or are working in environments where Chrome cannot be installed.

Use Cases

  • • AI-driven browser automation for testing and development workflows
  • • Performance profiling and Lighthouse auditing through AI agents
  • • Automated form filling, navigation, and interaction testing
  • • Network request inspection and debugging via natural language
  • • Device emulation and responsive design testing from AI coding tools
  • • Taking screenshots and analyzing page state during AI-assisted development

Not For

  • • Production web scraping at scale - designed for development workflows
  • • Non-Chrome browsers (Firefox, Safari, etc.)
  • • Headless-only environments without Chrome installed

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication for local use. Remote WebSocket connections support custom auth headers via --wsHeaders flag. Optional Google CrUX API used for performance metrics.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Apache 2.0 licensed. Official Google/Chrome project.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Usage statistics enabled by default - opt out with --no-usage-statistics
  • ⚠ Performance CrUX data sends URLs to Google by default - disable with --no-performance-crux
  • ⚠ Requires Node.js v20.19+ and Chrome stable
  • ⚠ Browser launches automatically on first tool use which may be unexpected
  • ⚠ Viewport max 3840x2160 in headless mode

Alternatives

Playwright MCP server Puppeteer Selenium with AI wrappers Browserbase MCP claude-in-chrome (browser extension approach)

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Chrome DevTools MCP.

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.

5215
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered