Terminate a running Chrome instance and close debugging connections to clean up resources and end debugging sessions.
MIT
132,654 tools. Last updated 2026-05-10 06:27
"Chrome DevTools - Browser Developer Tools & Debugging Resources" matching MCP tools:
- Restart Chrome to reset browser state, apply proxy settings, or recover from crashes by stopping and restarting the managed Chrome instance with remote debugging enabled.MIT
- Send raw Chrome DevTools Protocol commands to control browser behavior, modify page state, or access advanced debugging features when specialized tools are insufficient.MIT
- Retrieve console messages from Chrome DevTools to debug script errors, monitor page health, and inspect exception traces. Filter by severity level and optionally clear cache.MIT
- Release the Chrome DevTools Protocol connection after completing accessibility testing tasks, freeing up browser resources without terminating Chrome.MIT
- Debug HTTP failures, analyze request payloads, and inspect network sequences by capturing recent browser network requests, including errors missed by console tools.
Matching MCP Servers
- AlicenseAqualityCmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.Last updated262,108,3803Apache 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,108,38038,543
Matching MCP Connectors
Provides tools for searching Google Workspace documentation and much more.
Search GitHub, npm, PyPI, StackOverflow, ArXiv from one MCP — built for coding agents.
- Retrieve internal logs from the OpenTabs Chrome extension to view error messages, WebSocket events, and plugin injection warnings across all browser profiles without opening DevTools.
- Close and release resources from a Chrome browser session controlled by the MCP-Undetected-Chromedriver server, ensuring clean termination for web scraping, testing, and automation tasks.MIT
- Bypass bot detection by connecting to a real Chrome browser via CDP. Uses your existing profile and tabs to avoid fingerprinting.MIT
- Connect to a Chrome browser to access its accessibility tree for generating test selectors, performing audits, and reading element roles as a screen reader would.MIT
- Connect to any Chrome DevTools Protocol-compatible debugger (Node.js, Chrome, Edge) via WebSocket URL to start a new debugging session. Returns a session ID for all subsequent operations like breakpoints and variable inspection.Apache 2.0
- Capture screenshots of browser tabs for frontend development. Saves images to structured paths and returns them for analysis, requiring DevTools extension connection.
- Import authentication cookies from a Chrome browser via CDP to create an isolated Leapfrog profile with logged-in sessions and reCAPTCHA trust.MIT
- Open URLs in your preferred web browser. This tool launches web addresses in Firefox, Chrome, or your system's default browser, handling browser-specific configurations automatically.
- Generate realistic browser fingerprints for Chrome, Firefox, or Safari with User-Agent, headers, and platform information to create authentic browser profiles.
- Retrieve all open browser pages for automation, debugging, and performance analysis using Chrome DevTools.Apache 2.0
- Discover developer tools documented on getrecon.xyz by retrieving up to 20 tools with descriptions and URLs.MIT
- Attach to an active Chrome tab via remote debugging port to automate browser actions with Puppeteer.MIT
- Stop capturing network requests for a browser tab and release debugging resources to clear the request buffer.
- Start a browser connection to Chrome debugging ports for browser automation with persistent login sessions.MIT