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
521,397 tools. Updated 2026-09-06 11:00
"Debugging Chrome and HTML for Use with Playwright" matching MCP tools:
- Retrieve a snapshot of all running Chrome instances to obtain their instance IDs for use with other CDP debugging commands.MIT
- Launch Chrome with remote debugging and a fresh temporary profile. Choose between running alongside existing Chrome or starting with an empty profile.MIT
- Retrieve full HTML or contextual snippet around a search query from an active Chrome tab to inspect page structure, find elements by text, and verify rendering.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
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
- FlicenseAqualityCmaintenanceAn MCP server that enables LLMs to automate browser interactions using Playwright to fetch real-time Israeli weather data.4-
Matching MCP Connectors
- Chrome-StatsOAuth
Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.
Create sandboxed public-unlisted or access-key-protected HTML previews through a remote MCP server.
- List running Chrome processes on this machine, showing their CDP debugging ports. Use this to find a target before attaching to Chrome.MIT
- 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
- Extract Rappi credentials from Chrome and save them to .env. Attaches to an existing logged-in Chrome or launches a new window for manual login.MIT
- Connects to a debug-mode Chrome/Edge and returns open tab IDs, enabling browser automation. Auto-spawns a browser when no debugging endpoint is active.MIT
- Connect to or launch a debug-mode Chrome/Edge browser and retrieve open tab IDs to enable subsequent browser control actions.MIT
- Retrieve raw HTML source code from a page or a specific container for analyzing attributes, nesting, and debugging SSR or markup issues.MIT
- Scans common ports for Chrome/Edge instances with remote debugging enabled, returning a JSON list of discovered browsers.MIT
- Check that Chrome, Edge, or Playwright chromium is installed before running live URL accessibility audits against KWCAG 2.2. Confirms browser availability so audit_url calls don't fail.MIT
- Attach to an existing Chrome instance via CDP to control your current browser session without launching a new one. Avoid profile lock conflicts by connecting to Chrome started with a remote debugging port.MIT
- Terminate the active Chrome debugging session and clear the in-memory pause state. Use this before starting a new session to avoid stale state and breakpoint conflicts.MIT
- Lists Chrome page targets available for binding to WebGL debugging sessions, enabling selection of the correct context for frame capture and diagnostic analysis.MIT
- Opens a browser for automation, connecting to existing Chrome sessions or importing cookies from Firefox/Edge to preserve logins during automated tasks.GPL 3.0
- Load public URLs in your Chrome session to extract readability text, visible text, rendered HTML, or XHR responses, including from JavaScript-rendered and login-required pages.MIT
- Launch a dedicated Chrome with remote debugging, auto-detecting active ports. Use dryRun to preview, or set URL, port, and profile options.MIT
- Lists all open Chrome tabs with their debugging targets, prompting the user to choose which URL to debug before connecting.MIT