Checks if Chrome or Chromium is reachable through the remote debugging port using the Chrome DevTools Protocol.
MIT
279,175 tools. Last updated 2026-07-09 20:09
"Chrome DevTools - Browser Developer Tools & Debugging Resources" matching MCP tools:
- Gracefully terminates managed Chrome instance and closes all debugging connections. Use to clean up resources, prevent zombie processes, or end debugging sessions.MIT
- Restarts Chrome with remote debugging enabled; optionally configure proxy to reset browser state or recover from crashes.MIT
- Launches Chrome with remote debugging and a temporary profile. Supports newInstance (alongside existing Chrome) or freshSession (clean profile). Optionally copies cookies/logins from your Default profile.MIT
- Retrieve cached console messages from a Chrome tab for debugging script errors, monitoring page health, and inspecting exception traces. Optionally filter by severity level or clear the cache.MIT
- Send raw Chrome DevTools Protocol commands for advanced browser automation tasks not covered by standard tools. Returns the raw CDP response as JSON.MIT
Matching MCP Servers
- AlicenseAqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.Last updated4262,990,4643Apache 2.0
- Alicense-qualityBmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools. Provides browser automation, performance analysis, debugging capabilities, and network request monitoring.Last updated2,990,46446,490Apache 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.
- Ends the browser session and frees system resources by terminating the Chrome process.MIT
- Retrieve all open browser pages for automation, debugging, and performance analysis using Chrome DevTools.Apache 2.0
- 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
- 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.0
- Terminate the active browser session and release resources when finished using Upwork tools.Apache 2.0
- Perform fast QA audit on a URL via Chrome DevTools Protocol, detecting JS errors, network failures, API issues, and more for CI smoke tests and pre-deploy gates.MIT
- Connect to Chrome, Edge, or Brave via remote debugging port and retrieve open tab IDs. Automatically launches a debug-mode browser if no endpoint is detected.MIT
- Connect to a Chrome/Edge instance via CDP and retrieve open tab IDs. Automatically spawns a debug-mode browser if no endpoint is running.MIT
- Export captured network requests as a HAR 1.2 document for import into Chrome DevTools or Charles. Includes all requests from the full network ring.MIT
- Release the Chrome DevTools Protocol connection after completing accessibility testing tasks, freeing up browser resources without terminating Chrome.MIT
- Lists active parallel browser sessions with IDs and details to monitor automation workflows and manage resources in multi-browser testing.Apache 2.0