Skip to main content
Glama
557,992 tools. Updated 2026-09-13 09:15

"How to access browser console for debugging and error rectification" matching MCP tools:

  • Retrieve console logs from a Chrome tab to debug errors, monitor health, and inspect exceptions. Filter by severity and clear after retrieval.
    MIT
  • Retrieve browser console logs from Webvizio tasks when the task prompt lacks sufficient information for execution, providing additional context to complete development tasks.
    MIT
  • Guides setup and use of agent-browser CLI for automated browser tasks like navigating pages, clicking, and capturing console errors in a real browser.
    MIT
  • Execute JavaScript code directly in the browser console to automate web interactions, extract data, or manipulate page elements during browser automation sessions.
    MIT
  • Retrieve and filter browser console logs during automation testing to identify errors, warnings, and debug information with search and limit options.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides intelligent error detection and debugging capabilities across multiple programming languages with real-time monitoring of build, lint, runtime, console, and test errors. Offers AI-enhanced error analysis with automated resolution suggestions and context-aware debugging.
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Gives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.
    8
    -

Matching MCP Connectors

  • Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.

  • The official MCP Server from Mia-Platform to interact with Mia-Platform Console

  • Fetch console log entries from a specified browser tab, with optional regex filtering, error-only mode, and result limits to aid debugging.
    MIT
  • Collect a full debugging snapshot of the browser: current URL, title, console logs, alerts, and network requests with headers/body. Filter by URL, method, or console type to pinpoint issues.
    MIT
  • Verify server permissions to access iMessage data by checking Full Disk Access for chat.db and attachments directories, returning access status and macOS version for debugging.
    MIT
  • Retrieve browser console messages (log, warn, error) to debug JavaScript errors and inspect application logs. Filter by level or clear the buffer after reading.
    MIT
  • List all Google Search Console properties and sites you have access to, including verified domains and URL-prefix properties. Use it to retrieve the exact site_url required for other GSC tools.
    MIT
  • Decode Hedera blockchain error codes and receive debugging guidance to resolve transaction issues, understand error meanings, and find related security recommendations.
    Apache 2.0
  • Retrieve console log messages from browser tabs to monitor errors, warnings, and debug information during web application testing and development.
    MIT
  • Retrieve console error messages from a recorded session, ordered by time. Each error includes id, timestamp, level, message, and stack trace, with pagination support for long sessions.
    Apache 2.0
  • Retrieve the preceding user actions (clicks, typing, navigation) that led to a console error to understand its trigger.
    Apache 2.0
  • Debug broken pages by retrieving browser console errors and logs from a session. Buffer clears automatically for fresh data.
    AGPL 3.0