Skip to main content
Glama
133,407 tools. Last updated 2026-05-12 22:37

"chrome" 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
  • 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
  • Debug script execution from page load by enabling the debugger and injecting a breakpoint at the first statement of newly loaded scripts after reloading the page.
    MIT
  • Reload the current Chrome page to refresh content or reset to initial state, discarding unsaved changes and refetching server resources.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Other PDF MCP servers ask you to install Chrome, manage a local renderer, and ship templates yourself. Kamy MCP is a hosted endpoint — point any MCP client at https://mcp.kamy.dev/mcp, paste an API key, and start asking your AI to "generate an invoice for Acme Corp". Eight production-ready templates ship with the service (invoice, quote, receipt, contract, agreement, certificate, report, shipping-label)

  • Converts any URL to clean, LLM-ready Markdown using real Chrome browsers

  • Terminate a running Chrome instance and close debugging connections to clean up resources and end debugging sessions.
    MIT
  • Navigate the current Chrome tab to a specified URL to load new page content, changing the current page while discarding unsaved work.
    MIT
  • Execute JavaScript code in Chrome browser tabs to inspect dynamic content, manipulate DOM elements, or trigger complex interactions during 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
  • Capture runtime performance metrics like JS heap size and DOM node count from Chrome tabs to monitor memory usage, detect leaks, and profile performance.
    MIT
  • Send raw Chrome DevTools Protocol commands to control browser behavior, modify page state, or access advanced debugging features when specialized tools are insufficient.
    MIT
  • Retrieve HTTP requests and WebSocket frames from Chrome network activity to audit API calls, debug network issues, and inspect WebSocket traffic with filtering options.
    MIT
  • Activate proxy authentication for Chrome debugging by supplying credentials to handle authenticated proxy servers during browser automation.
    MIT
  • Analyze page performance by recording execution traces, calculating Core Web Vitals, and identifying long tasks to detect bottlenecks and optimize loading times.
    MIT
  • Capture screenshots of web pages for visual verification of UI state, layout, or rendering. Supports full-page or viewport captures with configurable image formats.
    MIT
  • Retrieve unhandled Chrome DevTools Protocol events from domains without specialized listeners. Filter by method name and limit results to monitor Target, Debugger, or custom domain activity during browser debugging.
    MIT
  • Screenshots a website to extract brand colors, fonts, and visual personality using headless Chrome. Resolves extraction failures on JS-rendered sites.
    MIT