Launch Chrome with remote debugging to enable use of Chrome DevTools MCP tools. Required before any other DevTools commands.
MIT
524,225 tools. Updated 2026-09-06 14:34
"Chrome DevTools - Browser Developer Tools & Debugging Resources" matching MCP tools:
- Attach to an already-running Chrome browser via DevTools Protocol for automation, preserving login state, cookies, and extensions. Enable remote debugging in Chrome first.MIT
- Close the active Chrome debugging instance and disconnect the DevTools MCP server.MIT
- Checks if Chrome or Chromium is reachable through the remote debugging port using the Chrome DevTools Protocol.MIT
- Execute arbitrary JavaScript in the current page to handle browser operations beyond standard automation tools. Access DOM APIs, storage, and same-origin resources for custom interactions.MIT
- Launches a persistent Chrome/Chromium session via CDP for browser automation. Call this first to enable navigation, clicks, and content extraction in subsequent operations.MIT
Matching MCP Servers
- AlicenseAqualityAmaintenanceControls a running Chrome/Chromium browser via the Chrome DevTools Protocol, enabling navigation, JavaScript evaluation, tab management, and raw CDP commands through MCP tools.5MIT
- AlicenseAqualityCmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.263,288,1653Apache 2.0
Matching MCP Connectors
Provides tools for searching Google Workspace documentation and much more.
65+ free in-browser developer tools (JSON, Base64, JWT, hash, regex…) callable over MCP.
- Fetch complete Chrome Web Store item details for an extension or theme, including rating, user count, version, developer, category, screenshots, and privacy links. Ideal for evaluating or comparing store listings.MIT
- Launch an isolated Chrome instance with its own profile and debugging port to separate browsing sessions, cookies, or proxies; returns an instance ID for targeted control.MIT
- Send raw CDP commands to the browser for advanced debugging and control, returning JSON responses. Use when specialized tools are insufficient.MIT
- Launch Chrome with remote debugging and a fresh temporary profile. Choose between running alongside existing Chrome or starting with an empty profile.MIT
- Restart a Chrome instance to reset browser state, apply proxy settings, or enable experimental WebMCP and WebGL capabilities.MIT
- Terminate a Chrome instance and close its debugging connections, cleaning up resources and preventing zombie processes. End a debugging session safely.MIT
- Ends the browser session and frees system resources by terminating the Chrome process.MIT
- Retrieve visible text from the current device screen, excluding browser chrome, for content analysis and automation workflows.MIT
- List managed Chrome browser profiles for a customer, including OS, platform, and user email.Apache 2.0
- Upload local files to browser file inputs using Chrome DevTools Protocol, bypassing the invisible native file picker that would hang the renderer.MIT
- Launches a Chrome session using nodriver to bypass bot detection, with optional proxy routing. Creates an isolated browser instance as the required first step for automated web testing.MIT
- Export captured network traffic as a HAR 1.2 JSON file for analysis in Chrome DevTools or other compatible tools. Converts browser network requests to standard format while maintaining security by redacting sensitive headers.MIT
- List running Chrome processes on this machine, showing their CDP debugging ports. Use this to find a target before attaching to Chrome.MIT
- Close the automated browser session to free resources. The browser reopens automatically on the next tool call.Apache 2.0Destructive
- Prepare Chrome or Edge for automated agent use by creating a dedicated profile and copying cookies, so the agent opens the browser with your sites logged in.GPL 3.0