Launch Chrome with remote debugging and a fresh temporary profile. Choose between running alongside existing Chrome or starting with an empty profile.
MIT
458,064 tools. Updated 2026-08-14 20:18
"Debugging Chrome and HTML for Use with Playwright" matching MCP tools:
- Search Coupang products using your own Chrome browser. No API key needed; just run Chrome with remote debugging enabled to open search results.MIT
- 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
- Connect to Chrome/Edge with remote debugging to retrieve open tab IDs, required before controlling tabs. Launches a debug browser if no endpoint is live.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
Create sandboxed public-unlisted or access-key-protected HTML previews through a remote MCP server.
Headless browser primitives for AI agents when sites need real JS rendering.
- 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
- Restarts Chrome with remote debugging, optionally setting proxy. Resets browser state, applies new proxy settings, or recovers from crashes.MIT
- Scans common ports for Chrome/Edge instances with remote debugging enabled, returning a JSON list of discovered browsers.MIT
- Retrieve the full HTML document of an active Chrome tab or a contextual snippet around a specific text query to inspect page structure and verify rendering.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
- 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
- Connect to an existing Chrome browser instance to retrieve the active tab URL and total tab count. Essential first step for interacting with pages and detecting handoff triggers.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 running Chrome browser via CDP to extract authentication cookies, enabling new browser instances to skip re-login.MIT
- Launch Chrome with remote debugging to enable use of Chrome DevTools MCP tools. Required before any other DevTools commands.MIT
- Fallback browser automation using Playwright when chrome-devtools is unavailable. Executes web actions and returns allowed actions for unknown requests.MIT