chrome-devtools-mcp-manager
Manage chrome-devtools-mcp service and OpenClaw's built-in Chrome browser for MCP-based browser automation. Use when user needs to use chrome-devtools-mcp functionality, ensure the browser is ready for MCP operations, or manage the browser/MCP lifecycle.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/andeymei/chrome-devtools-mcp-managerWhat This Skill Does
The chrome-devtools-mcp-manager skill serves as the central control plane for OpenClaw's integrated browser automation capabilities. By orchestrating both the OpenClaw built-in Chrome instance and the chrome-devtools-mcp server, this skill allows users to perform sophisticated browser-based tasks via the Model Context Protocol (MCP). It manages the lifecycle of the browser, ensuring that the necessary Chrome DevTools Protocol (CDP) ports (specifically port 18800) are open, accessible, and correctly configured for downstream MCP clients. Rather than manually managing browser instances, users can rely on this skill to handle process initiation, profile isolation via the 'openclaw' directory, and health verification.
Installation
To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/andeymei/chrome-devtools-mcp-manager
Ensure that you have the necessary MCP client dependencies configured, as this skill acts as the bridge between your agent's requests and the Chrome DevTools interface.
Use Cases
- Automated Web Interactions: Use the manager to spin up a browser for automated form filling or page navigation tasks.
- Browser Debugging: Leverage the CDP connection to inspect pages or capture network traffic for troubleshooting.
- MCP-Integrated Agents: Connect custom MCP clients to OpenClaw's browser to perform complex multi-step browser automation workflows.
- Session Management: Restart browsers cleanly to clear cookies and local storage between distinct automated testing sessions.
Example Prompts
- "Open the browser with the openclaw profile and navigate to google.com to start a research session."
- "Check if the built-in Chrome is currently running and verify that the CDP port 18800 is accessible."
- "Stop the current Chrome instance to clear the session and then restart it to a blank page."
Tips & Limitations
- Profile Isolation: Always specify the 'openclaw' profile to avoid interference with your standard personal browser instance.
- Port Conflicts: Ensure no other services are occupying port 18800, as this will prevent the MCP server from connecting to the Chrome DevTools interface.
- Memory Usage: Remember that keeping a browser running consumes system RAM; use the 'stop' action when automation tasks are completed.
- Protocol Version: This skill relies on the standard CDP protocol (v1.3); ensure your Chrome version is up to date for maximum compatibility with newer browser features.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-andeymei-chrome-devtools-mcp-manager": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-read, file-write