Retrieve a snapshot of all running Chrome instances to obtain their instance IDs for use with other CDP debugging commands.
MIT
648,543 tools. Updated 2026-10-07 19:19
"Debugging Chrome and HTML for Use with Playwright" matching MCP tools:
- 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
- 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
- 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
- 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
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
- FlicenseAqualityDmaintenanceAn 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.
Real-user Core Web Vitals for any website with enough traffic, from Google's Chrome UX Report…
- Terminate a Chrome instance and close its debugging connections, cleaning up resources and preventing zombie processes. End a debugging session safely.MIT
- Record a Playwright trace to capture browser interactions for offline debugging and replay with show-trace.Apache 2.0
- Launch TradingView Desktop with Chrome DevTools Protocol enabled for remote debugging. Auto-detects install location on Mac, Windows, and Linux.MIT
- List running Chrome processes on this machine, showing their CDP debugging ports. Use this to find a target before attaching to Chrome.MIT
- 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
- 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
- Connect to or launch a debug-mode Chrome/Edge browser and retrieve open tab IDs to enable subsequent browser control actions.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
- Diagnoses Ritoko startup or Chrome-launch issues by checking Node.js, SQLite, journal integrity, Playwright, and browser settings, returning pass, warn, or fail with fixes.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