Chrome Devtools Mcp
Use Chrome DevTools MCP for safe, configurable browser automation, page inspection, debugging, screenshots, network inspection, and performance analysis.
Rank
62
Safety
84
Downloads
981
Updated
Oct 11, 2026
Version
1.0.1
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 981 downloads reported by the source. Last updated 10/11/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 11, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 11, 2026
- Adoption signal
- 981 downloadsadoption · observed Oct 11, 2026
- Latest release
- 1.0.1release · observed Jun 23, 2026
- Handshake status
- UNKNOWNsecurity
What changed
Newest first. Only changes that point at a source are listed.
Release 1.0.1release
**Added starter example and install reference files.** - Added five new files: four configuration examples and one install reference. - Example configs demonstrate allowed domains, isolated mode, executable path use, and connecting to existing sessions. - Added a reference guide for MCP server installation and setup. - No changes to core skill behavior or requirements.
Observed Jun 23, 2026 · source
Install and run
Setup complexity: low.
clawhub skill install s17f3055gt9kyh956yeh3v8p0s87n9p8:chrome-devtools-mcp- Install using `clawhub skill install s17f3055gt9kyh956yeh3v8p0s87n9p8:chrome-devtools-mcp` in an isolated environment before connecting it to live workloads.
- No published capability contract is available yet, so validate auth and request/response behavior manually.
- Review the upstream CLAWHUB listing at https://clawhub.ai/aihlp/chrome-devtools-mcp before using production credentials.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/snapshot"
Run-check
$0.02 USD1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.
Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.
Documentation
CLAWHUB
62,830 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: chrome-devtools-mcp
description: Use Chrome DevTools MCP for safe, configurable browser automation, page inspection, debugging, screenshots, network inspection, and performance analysis.
metadata:
openclaw:
requires:
bins:
- node
- npm
config:
- chromeDevtools.mode
- chromeDevtools.browser
primaryConfig: chromeDevtools.mode
---
# Chrome DevTools MCP
Use this skill when an OpenClaw task requires controlled browser work through the official Chrome DevTools MCP server. Use it for page navigation, DOM inspection, console diagnostics, network diagnostics, screenshots, device emulation, and performance traces when those actions are part of the user's browser task.
This skill is a policy layer for Chrome DevTools MCP. It does not implement a new MCP server and does not replace OpenClaw MCP server configuration. The MCP server must be configured separately under OpenClaw `mcp.servers` before this skill can use the tools.
Do not use this skill for unauthorized access-control bypass, CAPTCHA solving, credential theft, token harvesting, session hijacking, or unattended actions outside the user's authorization. Debugging an authorized site may require inspecting cookies, storage, request headers, and authentication flows; that is allowed when it is task-relevant and configured by the user.
## Required runtime
Required local binaries:
- `node`
- `npm`
Official MCP server command:
```bash
npx -y chrome-devtools-mcp@latest
```
The official primary target is current stable Chrome or newer. Chrome for Testing may be used when configured. Chromium is compatibility mode and must be selected through an explicit executable path or browser configuration.
## Required OpenClaw MCP server definition
Before using this skill, OpenClaw must have an enabled MCP server definition named `chrome-devtools` or an equivalent configured server selected by the user.
Default isolated stdio definition:
```json5
{
mcp: {
servers: {
"chrome-devtools": {
enabled: true,
transport: "stdio",
command: "npx",
args: [
"-y",
"chrome-devtools-mcp@latest",
"--isolated",
"--no-usage-statistics",
"--no-performance-crux"
],
connectTimeout: 20,
timeout: 120,
supportsParallelToolCalls: false
}
}
}
}
```
If OpenClaw reports `missing transport` or `invalid`, the MCP definition is incomplete. Add `transport: "stdio"`, `command: "npx"`, and the required `args` array, then save/publish and run `openclaw mcp reload`.
## Configuration model
Read the user configuration before using this skill. The expected top-level object is `chromeDevtools`.
Default safe configuration:
```json
{
"chromeDevtools": {
"mode": "isolated",
"browser": "chrome",
"executablePath": null,
"userDataDir": null,
"browserUrl": null,
"headless": false,
"isolated": true,
"allowedUrlPatternREADME.md
# chrome-devtools-mcp
OpenClaw skill package for safe, configurable use of the official Chrome DevTools MCP server.
This skill does not decide one fixed browser setup for everyone. It gives OpenClaw a browser-control policy.
The user chooses:
- isolated browser or existing session
- Chrome, Chrome for Testing, Chromium, or custom executable
- temporary profile or specific profile directory
- allowed and blocked URLs
- whether the agent may inspect cookies/storage
- whether the agent may submit forms or perform account-changing actions
The default is safest:
- isolated Chrome
- temporary profile
- cookie/storage inspection allowed for debugging, with secret values redacted by default
- form submission allowed only when configured and task-relevant
- no destructive actions without explicit confirmation
- telemetry disabled
## Critical distinction
Installing this skill is not enough to make Chrome DevTools MCP usable.
OpenClaw must also have an enabled MCP server definition under `mcp.servers`. If the UI shows a custom server with `missing transport`, the server is not configured and the agent cannot use Chrome DevTools MCP tools.
Use this default OpenClaw MCP server definition:
```json5
{
mcp: {
servers: {
"chrome-devtools": {
enabled: true,
transport: "stdio",
command: "npx",
args: [
"-y",
"chrome-devtools-mcp@latest",
"--isolated",
"--no-usage-statistics",
"--no-performance-crux"
],
connectTimeout: 20,
timeout: 120,
supportsParallelToolCalls: false
}
}
}
}
```
After saving/publishing the MCP config, run:
```bash
openclaw mcp reload
openclaw mcp status --verbose
openclaw mcp doctor --probe
openclaw mcp probe chrome-devtools
```
## Package structure
```text
chrome-devtools-mcp/
SKILL.md
README.md
references/
configuration.md
browser-modes.md
security-policy.md
user-settings.md
skillspector.md
openclaw-mcp-install.md
examples/
mcp.chrome.isolated.json
mcp.chromium.executable.json
mcp.existing-session.json
mcp.allowed-domain.json
user-settings.example.json
openclaw.mcp.chrome.isolated.json5
openclaw.mcp.chromium.executable.json5
openclaw.mcp.existing-session.json5
openclaw.mcp.allowed-domain.json5
scripts/
validate_skill.py
```
## What this skill provides
This package provides instructions, configuration examples, security rules, validation checks, and publishing guidance for using Chrome DevTools MCP inside OpenClaw.
It does not implement a new MCP server. It wraps and documents correct use of the official `chrome-devtools-mcp` server.
Default MCP command:
```bash
npx -y chrome-devtools-mcp@latest
```
Default safe mode:
```bash
npx -y chrome-devtools-mcp@latest \
--isolated \
--no-usage-statistics \
--no-performance-crux
```
## Browser modes
### 1. Isolated Chrome session
Default mode. Use it for normal browser_meta.json
{
"ownerId": "kn729zr4mqh2smddqkt2n64q5x87mha0",
"slug": "chrome-devtools-mcp",
"version": "1.0.1",
"publishedAt": 1782203875780
}references/browser-modes.md
# Browser modes ## isolated Default mode. Use for normal browser work when the task does not require a pre-existing login state. Properties: - temporary profile - avoids normal user profile - lowest-risk default - suitable for navigation, inspection, screenshots, console/network debugging, and performance traces MCP server args: ```text -y chrome-devtools-mcp@latest --isolated --no-usage-statistics --no-performance-crux ``` ## executable Use when the user chooses Chrome, Chrome for Testing, Chromium, or a custom compatible executable. Properties: - explicit browser executable - explicit user data directory - Chromium is compatibility mode - dedicated automation profile is required unless the user explicitly chooses a specific real profile MCP server args: ```text -y chrome-devtools-mcp@latest --executable-path=<configured_browser_path> --user-data-dir=<configured_profile_dir> --no-usage-statistics --no-performance-crux ``` ## existing-session Use only when the user explicitly needs a running authenticated browser. Properties: - higher risk than isolated mode - can access open tabs and signed-in state - requires localhost-only browser URL - requires explicit policy setting `allowExistingSession: true` MCP server args: ```text -y chrome-devtools-mcp@latest --browser-url=http://127.0.0.1:<port> --no-usage-statistics --no-performance-crux ``` Rejected endpoint examples: ```text http://0.0.0.0:9222 http://192.168.1.10:9222 http://example.com:9222 ``` Allowed endpoint examples: ```text http://127.0.0.1:9222 http://localhost:9222 http://[::1]:9222 ```
references/configuration.md
# Configuration
This skill uses two configuration layers.
## 1. OpenClaw MCP server configuration
This controls whether Chrome DevTools MCP exists as a usable MCP server.
Required fields for local stdio mode:
```json5
{
mcp: {
servers: {
"chrome-devtools": {
enabled: true,
transport: "stdio",
command: "npx",
args: ["-y", "chrome-devtools-mcp@latest", "--isolated", "--no-usage-statistics", "--no-performance-crux"]
}
}
}
}
```
Without this configuration, the skill can provide policy instructions but cannot operate the browser.
## 2. User policy configuration
This controls browser mode, browser type, profile, allowed URLs, protected data, and confirmation gates.
See `references/user-settings.md` and `examples/user-settings.example.json`.
## Required command
```bash
npx -y chrome-devtools-mcp@latest
```
## Default arguments
```text
--isolated
--no-usage-statistics
--no-performance-crux
```
## Mode-specific arguments
Isolated:
```text
--isolated
--no-usage-statistics
--no-performance-crux
```
Executable:
```text
--executable-path=<configured_browser_path>
--user-data-dir=<configured_profile_dir>
--no-usage-statistics
--no-performance-crux
```
Existing session:
```text
--browser-url=http://127.0.0.1:<port>
--no-usage-statistics
--no-performance-crux
```AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
- Card JSON
- Facts JSON
- Snapshot JSON
- Contract JSON
- Trust JSON
- Changes JSON
- Warnings JSON
- Seen by JSON
- Disagreements JSON
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/aihlp/skills/chrome-devtools-mcp",
"sourceUrl": "https://clawhub.ai/aihlp/skills/chrome-devtools-mcp",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T22:53:19.423Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T22:53:19.423Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "981 downloads",
"href": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceUrl": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T22:53:19.423Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "1.0.1",
"href": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceUrl": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-06-23T08:37:55.780Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 1.0.1",
"description": "**Added starter example and install reference files.** - Added five new files: four configuration examples and one install reference. - Example configs demonstrate allowed domains, isolated mode, executable path use, and connecting to existing sessions. - Added a reference guide for MCP server installation and setup. - No changes to core skill behavior or requirements.",
"href": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceUrl": "https://clawhub.ai/aihlp/chrome-devtools-mcp",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-06-23T08:37:55.780Z",
"isPublic": true
}
]
}Record generated Oct 12, 2026.
For crawlers
This page is free to read. The run-check above is the only paid part, and it answers HTTP 402 until it is paid. Everything else here is public.
- One record, as JSON: card, facts, snapshot, contract, trust, changes, warnings, seen by, disagreements.
- Every agent, one feed: /.well-known/ai-catalog.json
- What this site sells, and the price: /.well-known/x402
- Paid run-check: /api/v1/agents/clawhub-aihlp-chrome-devtools-mcp/run-check
