Chrome Debug MCP

MCP server that exposes Chrome DevTools Protocol (CDP) capabilities to AI agents, enabling agents to attach to Chrome browser sessions, inspect DOM elements, capture network traffic, execute JavaScript in page context, take screenshots, and perform debugging operations through structured MCP tool calls.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools chrome devtools debugging browser mcp-server cdp chrome-devtools-protocol
⚙ Agent Friendliness
74
/ 100
Can an agent use this?
🔒 Security
75
/ 100
Is it safe for agents?
⚡ Reliability
64
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
65
Error Messages
63
Auth Simplicity
100
Rate Limits
90

🔒 Security

TLS Enforcement
80
Auth Strength
72
Scope Granularity
70
Dep. Hygiene
72
Secret Handling
80

Full browser session access including cookies, passwords stored in page context, and authenticated sessions. Keep debugging port local only. High-trust tool for development environments.

⚡ Reliability

Uptime/SLA
62
Version Stability
65
Breaking Changes
62
Error Recovery
65
AF Security Reliability

Best When

A developer agent needs to debug live web applications by inspecting Chrome's DevTools data — inspecting DOM, capturing network traffic, or executing JS in page context for debugging workflows.

Avoid When

You need full browser automation (navigation, form filling) — use Playwright or Puppeteer MCPs which handle the full automation lifecycle better.

Use Cases

  • Debugging web applications by inspecting DOM state from debugging agents
  • Capturing and analyzing network requests in Chrome from performance agents
  • Executing JavaScript in browser context from test automation agents
  • Taking page screenshots and analyzing visual state from QA agents

Not For

  • Full browser automation (use Playwright MCP or Puppeteer MCP for end-to-end automation)
  • Production environments without Chrome installed
  • Non-Chrome browsers (Firefox, Safari need different DevTools protocols)

Interface

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

Authentication

Methods: none
OAuth: No Scopes: No

No authentication — attaches to locally running Chrome with remote debugging enabled. Requires Chrome launched with --remote-debugging-port flag.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source Chrome DevTools Protocol MCP bridge.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Chrome must be launched with --remote-debugging-port=9222 flag before connecting
  • JS execution in page context can modify page state — use carefully in production debugging
  • Chrome updates can change CDP behavior — test with each Chrome version update
  • Only attaches to one Chrome tab/session at a time by default

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Chrome Debug MCP.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

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

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered