Skip to main content
Glama
clusslin

browser-console-mcp-tools

by clusslin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to browser-console-mcp-tools

No user-submitted related servers found.

    Related Servers

    • console-stream-mcp

      Topman-14
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to access live console logs, errors, and network requests from web applications via a local WebSocket connection, without copying data to chat.
      7 npm
      18
      MIT

    • pigeon

      pepperonas
      A
      license
      Not graded
      quality
      D
      maintenance
      Forwards browser console errors, warnings, and unhandled rejections to Claude Code via MCP, enabling natural language debugging.
      6 npm
      MIT

    • mcp-console-hub

      nano-step
      A
      license
      Not graded
      quality
      D
      maintenance
      Streams browser DevTools console, network, storage, and performance data to your IDE's AI agent for real-time debugging and analysis.
      8 npm
      1
      MIT

    • Metro Logs MCP

      igorzheludkov
      A
      license
      B
      quality
      A
      maintenance
      Captures and provides access to React Native console logs from Metro bundler, enabling AI assistants to retrieve, filter, and search app logs in real-time without manual copy/paste.
      64
      1,506 npm
      75
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    get_console_messages and get_console_errors overlap since errors are a subset of messages filterable by type='error', but the errors tool adds distinct value (stack traces, detailed error info), so the boundary is defensible. clear_console_messages and get_console_stats are clearly distinct.

    Naming Consistency5/5

    All four tools follow a consistent snake_case verb_noun pattern (get_, get_, clear_, get_). The convention is predictable and readable throughout.

    Tool Count5/5

    Four tools is well-scoped for a browser console inspection purpose: two retrieval variants, one clear, one stats. Each earns its place with no bloat.

    Completeness4/5

    Read, filtered read, clear, and stats cover the core console lifecycle. Minor gap: no way to wait/subscribe for new messages or export logs, but agents can poll existing tools to work around this.

    Resources