Chrome DevTools MCP Bridge
Guidance for using the external Chrome DevTools MCP server from an MCP-capable client. The upstream project is ChromeDevTools/chrome-devtools-mcp (Apache-2.0). It is not vendored or redistributed here; install and license it under its own terms.
Procedure
Prerequisites
- Install and run the MCP server by following its upstream README.
- Start Chrome so the server can attach, or let the server manage the browser.
- Register the server in your MCP client and confirm it lists tools.
- Treat tool names and arguments as version-specific: read the live tool list
rather than assuming a fixed catalog.
Workflow
- Navigate, then take an accessibility snapshot before acting.
- Act through the snapshot's element references, not guessed coordinates.
- After each action, re-snapshot and check console and network for errors.
- Use screenshots for visual claims; use the DOM snapshot for structural ones.
- Start a performance trace before the interaction and stop it after, then
analyze the result.
Capability areas
| Area | Typical operations |
|---|---|
| Pages | navigate, create, select, close |
| Inspection | accessibility snapshot, screenshot, click, hover, fill, drag |
| Console | list messages, inspect one message |
| Network | list requests, inspect one request |
| Script | evaluate in page, type text, fill forms, press keys |
| Performance | start and stop traces, analyze insights, emulate device or network |
| Audit | Lighthouse-style audit, heap snapshot |
The exact set varies by server version. Confirm before scripting.
Separation from desktop automation
Use this server for web pages, DevTools, network, and console. Use a desktop automation tool for native windows. Do not use either where the other is the actual target.
Limits and safety
- The server can execute page scripts; scope it to test profiles and non-sensitive
accounts.
- Network traces and snapshots may contain credentials or personal data. Redact
before sharing.
- A failed connection usually means the browser was not started with debugging
enabled or the client points at the wrong port.
- The repo does not test a specific server version; compatibility is your check.
Anti-patterns
- Using this for native-app automation.
- Clicking by pixel coordinates when a snapshot reference exists.
- Relying on a screenshot where the DOM would answer the question.
- Pasting raw network traces into a shared document without redaction.
Verification Checklist
- [ ] The MCP client lists the server's tools for the installed version.
- [ ] A snapshot reference, not a guess, was used for the interaction.
- [ ] Console and network were checked after the action.
- [ ] Traces and screenshots are redacted before sharing.