Skip to main content
Glama
127,142 tools. Last updated 2026-05-05 09:29

"MCP server for browser automation via Chrome DevTools" matching MCP tools:

  • Send raw Chrome DevTools Protocol commands to control browser behavior, modify page state, or access advanced debugging features when specialized tools are insufficient.
    MIT
  • Activate proxy authentication for Chrome debugging by supplying credentials to handle authenticated proxy servers during browser automation.
    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
  • Update Chrome Web Store listing metadata through UI automation when API updates fail or as the primary method due to v1 API deprecation.
    MIT
  • Migrates Next.js applications to Cache Components mode. Automatically configures settings, starts dev server, detects errors via browser automation, adds Suspense boundaries and 'use cache' directives, and verifies zero errors.
    MIT
  • Switch browser runtime mid-session to match task: headless for fast, no-login automation; Chrome for using real user login sessions on authenticated sites and write operations.

Matching MCP Servers

Matching MCP Connectors

  • Create a persistent browser session for executing Python or JavaScript code that interacts with live web pages, enabling multi-step browser automation and maintaining state across multiple operations.
  • 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.
  • Force Chrome extension to disconnect and reconnect to the MCP server, recovering from stale connections without requiring a full extension reload.
  • 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
  • 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.
  • 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
  • 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
  • Locate the Chrome extension directory path to manually install browser extensions for automation testing and development purposes.
    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
  • Generate realistic browser fingerprints for Chrome, Firefox, or Safari with User-Agent, headers, and platform information to create authentic browser profiles.