chrome devtools
- Repo stars 42,728
- Author repo chrome-devtools-mcp
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @ChromeDevTools · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
## Core Concepts
**Browser lifecycle**: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration: `npx chrome-devtools-mcp@latest --help`.
Addional tooling can be enabled by providing the following flags:
- For extension tooling, use the `--categoryExtensions` flag.
- For memory tooling, use the `--memoryDebugging` flag.
**Page selection**: Tools operate on the currently selected page. Use `list_pages` to see available pages, then `select_page` to switch context.
**Element interaction**: Use `take_snapshot` to get page structure with element `uid`s. Each element has a unique `uid` for interaction. If an element isn't found, take a fresh snapshot - the element may have been removed or the page changed.
## Workflow Patterns
### Before interacting with a page
1. Navigate: `navigate_page` or `new_page`
2. Wait: `wait_for` to ensure content is loaded if you know what you look for.
3. Snapshot: `take_snapshot` to understand page structure
4. Interact: Use element `uid`s from snapshot for `click`, `fill`, etc.
### Efficient data retrieval
- Use `filePath` parameter for large outputs (screenshots, snapshots, traces)
- Use pagination (`pageIdx`, `pageSize`) and filtering (`types`) to minimize data
- Set `includeSnapshot: false` on input actions unless you need updated page state
### Tool selection
- **Automation/interaction**: `take_snapshot` (text-based, faster, better for automation)
- **Visual inspection**: `take_screenshot` (when user needs to see visual state)
- **Additional details**: `evaluate_script` for data not in accessibility tree
### Parallel execution
You can send multiple tool calls in parallel, but maintain correct order: navigate → wait → snapshot → interact.
### Testing an extension
1. **Install**: Use `install_extension` with the path to the unpacked extension.
2. **Identify**: Get the extension ID from the response or by calling `list_extensions`.
3. **Trigger Action**: Use `trigger_extension_action` to open the popup or side panel if applicable.
4. **Verify Service Worker**: Use `evaluate_script` with `serviceWorkerId` to check extension state or trigger background actions.
5. **Verify Page Behavior**: Navigate to a page where the extension operates and use `take_snapshot` to check if content scripts injected elements or modified the page correctly.
## Troubleshooting
If `chrome-devtools-mcp` is insufficient, guide users to use Chrome DevTools UI:
- https://developer.chrome.com/docs/devtools
- https://developer.chrome.com/docs/devtools/ai-assistance
If there are errors launching `chrome-devtools-mcp` or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.
Sections and files
Listed in source order.
sections -> Core Concepts → Workflow Patterns → Before interacting with a page → Efficient data retrieval → Tool selection → Parallel execution
terms -> Browser lifecycle · Page selection · Element interaction · Automation/interaction · Visual inspection · Additional details · Install · Identify
files/cmd -> npx chrome-devtools-mcp@latest --help · --categoryExtensions · --memoryDebugging · list_pages · select_page · take_snapshot · uid · navigate_page
body sha256 -> 4595ad35cb98
Core Concepts
Browser lifecycle: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration:
npx chrome-devtools-mcp@latest --help. Addional tooling can be enabled by providing the following flags: For extension tooling, use the--categoryExtensionsflag. For memory tooling, use the--memoryDebuggingflag. Page selection: Tools operate on the currently selected page. Uselist_pagesto see available pages, thenselect_pageto switch context.Before interacting with a page
Navigate:
navigate_pageornew_pageWait:wait_forto ensure content is loaded if you know what you look for. Snapshot:take_snapshotto understand page structure Interact: Use elementuids from snapshot forclick,fill, etc.Efficient data retrieval
Use
filePathparameter for large outputs (screenshots, snapshots, traces) Use pagination (pageIdx,pageSize) and filtering (types) to minimize data SetincludeSnapshot: falseon input actions unless you need updated page stateTool selection
Automation/interaction:
take_snapshot(text-based, faster, better for automation) Visual inspection:take_screenshot(when user needs to see visual state) Additional details:evaluate_scriptfor data not in accessibility treeParallel execution
You can send multiple tool calls in parallel, but maintain correct order: navigate → wait → snapshot → interact.