Skip to main content
Glama
604,423 tools. Updated 2026-09-23 19:45

"How to Read the Browser Console" matching MCP tools:

  • Retrieves browser console logs (errors, warnings, GM_log) to diagnose script runtime errors after reload. Saves full log to .customaise/console-context.json, or returns inline without a file.
    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
    Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
    72 npm
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
    -

Matching MCP Connectors

  • Browser compatibility and Baseline status for any web feature — offline, from bundled MDN data.

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

  • Read any UE console variable by name, returning its value in all four representations, detected type, read-only flag, and last-setter. Inspect CVar state without invoking the console exec engine.
    MIT
  • Close the browser and wipe all session state—tabs, references, and console logs—to start fresh. For CDP connections, detach without terminating the browser.
    MIT
  • Clear the console buffer to ensure subsequent output reflects only the next action. Leaves the browser's developer console display untouched.
    MIT
  • Retrieve console log messages from browser tabs to monitor errors, warnings, and debug information during web application testing and development.
    MIT
  • Retrieve browser console messages to uncover stack traces, debug URLs, and CSP violations invisible to the proxy. Filter by level and clear the buffer after reading.
    MIT
  • Opens a URL in the browser and starts capturing console and network errors. Returns page title, HTTP status, and active engine; set the engine option to compare rendering.
    MIT
  • Read browser console logs and filter them by level or regex pattern, with an option to clear the buffer after reading.
    MIT
  • Retrieve browser console logs or evaluate JavaScript expressions to debug and interact with web pages.
    MIT
  • Retrieve browser console messages from a specific tab, filter with a regex pattern, and debug JavaScript errors or review application logs without noise.
    Apache 2.0
  • Toggle console capture on a browser tab. Buffers up to 500 console messages (log, info, warn, error, debug) for retrieval via zen_console_logs.
    MIT
  • Diagnose rendering issues and JavaScript errors in web apps by capturing a screenshot and browser console logs.
    BSD 3-Clause