Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Chrome DevTools MCP — Google's official browser automation and testing server. Control Chrome via Puppeteer through MCP protocol: click, fill forms, navigate...
Chrome DevTools MCP — Google's official browser automation and testing server. Control Chrome via Puppeteer through MCP protocol: click, fill forms, navigate...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Google's official Chrome DevTools MCP server — gives AI agents full control of a live Chrome browser via Puppeteer and the Chrome DevTools Protocol.
Input automation — click, drag, fill forms, hover, press keys, upload files, handle dialogs Navigation — open/close/switch pages, wait for elements/network idle Screenshots & snapshots — capture page state visually and as DOM Performance traces — record and analyze Chrome performance traces with insights Network inspection — list/inspect network requests and responses Console debugging — read console messages with source-mapped stack traces Device emulation — emulate mobile devices, resize viewport Form automation — fill multiple form fields at once
Node.js v20.19+ (already available in OpenClaw) Chrome/Chromium browser
npx -y chrome-devtools-mcp@latest --help
# Standard (launches Chrome automatically) npx -y chrome-devtools-mcp@latest # Headless mode (for servers) npx -y chrome-devtools-mcp@latest --headless # Connect to existing Chrome (must be started with --remote-debugging-port=9222) npx -y chrome-devtools-mcp@latest --browser-url=http://127.0.0.1:9222 # Disable telemetry npx -y chrome-devtools-mcp@latest --no-usage-statistics --no-performance-crux
Add to your openclaw.json under MCP servers: { "mcp": { "servers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest", "--headless", "--no-usage-statistics"] } } } } Or use the setup script: python3 {baseDir}/scripts/setup_chrome_mcp.py setup python3 {baseDir}/scripts/setup_chrome_mcp.py status python3 {baseDir}/scripts/setup_chrome_mcp.py test
ToolDescriptionKey ParamsclickClick an elementuid (required), dblClickdragDrag element onto anotherfrom_uid, to_uidfillType text into input/textarea/selectuid, valuefill_formFill multiple form elements at onceelements[]handle_dialogAccept/dismiss browser dialogsaction (accept/dismiss)hoverHover over elementuidpress_keyPress keyboard keykeyupload_fileUpload file to inputuid, paths[]
ToolDescriptionKey Paramsnavigate_pageGo to URLurlnew_pageOpen new taburlclose_pageClose current tab—list_pagesList all open tabs—select_pageSwitch to tabindexwait_forWait for element/networkevent, uid, timeout
ToolDescriptiontake_screenshotCapture page as imagetake_snapshotGet DOM/accessibility snapshotevaluate_scriptRun JavaScript in pagelist_console_messagesGet console log entriesget_console_messageGet specific console message
ToolDescriptionperformance_start_traceBegin performance recordingperformance_stop_traceStop and get trace dataperformance_analyze_insightAI analysis of trace
ToolDescriptionlist_network_requestsList all network requestsget_network_requestGet request/response details
ToolDescriptionemulateEmulate device (mobile, tablet)resize_pageChange viewport size
navigate_page → URL take_snapshot → get element UIDs click/fill → interact with elements take_screenshot → capture result
navigate_page → URL performance_start_trace Interact with page performance_stop_trace performance_analyze_insight
navigate_page → form URL take_snapshot → identify form fields fill_form → fill all fields at once click → submit button take_screenshot → verify result
Google collects usage statistics by default — disable with --no-usage-statistics Performance tools may send trace URLs to Google CrUX API — disable with --no-performance-crux Avoid sharing sensitive data in browser sessions
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.