Skip to main content
Glama
134,573 tools. Last updated 2026-05-23 07:28

"Debugging Chrome and HTML for Use with Playwright" matching MCP tools:

  • Launches Chrome with remote debugging enabled, using a temporary profile. Select mode: newInstance to run alongside existing Chrome, or freshSession for a clean profile.
    MIT
  • Connect to a remote-debugging Chrome or Edge instance, retrieve open tab IDs, and optionally auto-launch a debug-mode browser when no endpoint is live. Returns tab details including id, url, title, and active status.
    MIT
  • Restart Chrome to reset browser state, apply proxy settings, or recover from crashes by stopping and restarting the managed Chrome instance with remote debugging enabled.
    MIT
  • Terminate a running Chrome instance and close debugging connections to clean up resources and end debugging sessions.
    MIT
  • Retrieve full HTML documents or contextual snippets from active Chrome tabs to inspect page structure, find elements by text, or verify rendering without side effects.
    MIT
  • Bypass bot detection by connecting to a real Chrome browser via CDP. Uses your existing profile and tabs to avoid fingerprinting.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Headless browser primitives for AI agents when sites need real JS rendering.

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • 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
  • 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
  • Connect to a running Chrome/Chromium instance with CDP enabled for browser automation and debugging.
  • Run arbitrary JavaScript in the Playwright server to automate browser interactions. Warning: this tool executes code with full server access, equivalent to remote code execution.
  • Fetch raw HTML content from any URL with optional JavaScript rendering for dynamic websites and Single Page Applications.
    MIT
  • Resolves HTML input for Figma builds by classifying, rendering client-rendered pages if needed, and returning a validated HTML file path. Use outputPath if status is READY; report error if FAILURE.
    MIT
  • Execute Playwright browser automation code to interact with web pages, enabling automated testing and data extraction through JavaScript functions.
    Apache 2.0
  • Execute custom Playwright code snippets to interact with web pages, automate browser actions, and retrieve page data. Ideal for AI-driven browser testing and integration with Cloudflare Workers.
    Apache 2.0