Launch Chrome with remote debugging to enable use of Chrome DevTools MCP tools. Required before any other DevTools commands.
MIT
701,312 tools. Updated 2026-10-25 11:33
"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
- Launch a persistent SeleniumBase browser session via CDP for automation workflows. Required before using interaction tools, preserving state across sessions.MIT
- Mints a single-use connect URL for Spicrawl's remote browser, letting your code drive it via Puppeteer or Playwright over Chrome DevTools Protocol.Apache 2.0
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.262,262,793 npm3Apache 2.0
Matching MCP Connectors
Provides tools for searching Google Workspace documentation and much more.
Official ImageKit developer server: search the docs and build transformation URLs. No sign-in.
- Open an independent Chrome instance with its own profile and debugging port to isolate browsing sessions, cookies, proxies, or WebMCP contexts; returns instance_id for other tools.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
- Stop and restart a selected Chrome instance with remote debugging enabled to reset browser state, apply proxy settings, enable capability presets, or recover from crashes.MIT
- Terminate a Chrome instance and close its debugging connections, cleaning up resources and preventing zombie processes. End a debugging session safely.MIT
- Terminate orphaned Chrome browser instances that remain after their MCP agent disconnects, freeing system resources.Apache 2.0Destructive
- List managed Chrome browser profiles for a customer, including OS, platform, and user email.Apache 2.0
- Fetch detailed Chrome Web Store extension or theme data by ID, including ratings, users, version, size, languages, developer, category, screenshots, and privacy links.MIT
- Retrieve visible text from the current device screen, excluding browser chrome, for content analysis and automation workflows.MIT
- Track recent Chrome Web Store item changes by type—users, rating, version, developer, permissions, privacy, or status—and return up to 500 observations with changed figures.MIT
- Upload local files to browser file inputs using Chrome DevTools Protocol, bypassing the invisible native file picker that would hang the renderer.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
- Check if a Chrome instance with a remote debugging port is available for LinkedIn session recovery. Reports status or the command to launch Chrome correctly.Academic Free v1.1
- 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