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
127,144 tools. Last updated 2026-05-05 09:48
"An MCP for interacting with Google Chrome DevTools and aiding in scraping" matching MCP tools:
- Assess an entity's trust score and tier to evaluate risk before interacting with unknown agents.MIT
- Release the Chrome DevTools Protocol connection after completing accessibility testing tasks, freeing up browser resources without terminating Chrome.MIT
- Click web page elements using CSS selectors to submit forms, toggle buttons, or navigate. Returns element details after triggering trusted mouse events via Chrome DevTools Protocol.
- Save authentication tokens for NotebookLM when the automated CLI method fails. Use this fallback tool to manually input cookie headers from Chrome DevTools to establish secure access.MIT
- Retrieve all open Google Chrome tabs with unique, persistent IDs for reliable identification and management. Output includes both display format and Tab ID for consistent operations via the MCP Browser Tabs Server.MIT
Matching MCP Servers
- Alicense-quality-maintenanceEnables AI coding assistants to control and inspect a live Chrome browser through DevTools for automated testing, performance analysis, debugging, and web scraping. Provides reliable browser automation using Puppeteer with comprehensive DevTools access.Last updated1,413,2023
- Alicense-qualityBmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.Last updated297MIT
Matching MCP Connectors
Web scraping for AI agents. Extract text and metadata from any URL worldwide. $0.005/page.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
- 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
- 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.
- 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
- 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
- Opens Google Maps in Chrome to visually search and review locations for inspiration, filtering out map tiles and preventing downloads of Google-hosted previews.MIT
- Refresh the currently open Chrome app on macOS to apply changes or restart the application.MIT
- Launch Chrome browser with stealth mode to access Suno AI for music generation, supporting headless operation for automation workflows.MIT
- Attach to an active Chrome tab via remote debugging port to automate browser actions with Puppeteer.MIT
- Execute Chrome DevTools Protocol commands to control browser tabs for automation tasks like debugging, testing, or data extraction.MIT
- Retrieve Chrome DevTools Protocol endpoints and tab targets for attaching Playwright or DevTools to a launched Chrome instance.
- List and filter browser cookies from Chrome DevTools sessions with pagination and value truncation for network traffic analysis and debugging.
- Launch a Chrome/Chromium browser with Chrome DevTools Protocol enabled for browser automation, creating an isolated profile directory for testing and development.
- Close a Chrome DevTools debugging session by specifying its session ID to end network traffic interception and monitoring.