Skip to main content
Glama
tznthou

Simple Console MCP

by tznthou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Simple Console MCP

No user-submitted related servers found.

    Related Servers

    • MCP Browser Logger

      tao-Lionel
      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.
      -

    • Browser Runtime MCP

      MakiDevelop
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor and debug browser runtime errors, console logs, and page diagnostics in real time via a Chrome extension and local MCP server.
      4
      MIT

    • bwb-browser

      krshforever
      A
      license
      B
      quality
      A
      maintenance
      A lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.
      26
      25 npm
      15
      MIT

    • xfactor

      fveiraswww
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.
      -
    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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: execute_js runs JavaScript, get_console_logs retrieves logs, list_targets enumerates browser targets, and navigate handles URL navigation. The descriptions reinforce these unique functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (execute_js, get_console_logs, list_targets, navigate), using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count5/5

    With 4 tools, this server is well-scoped for a simple console MCP, covering core browser automation tasks (execution, logging, target listing, navigation). Each tool earns its place without feeling thin or bloated, aligning with the server's focused purpose.

    Completeness4/5

    The toolset provides solid coverage for basic browser console operations, including execution, monitoring, target management, and navigation. A minor gap exists in lacking tools for more advanced interactions like element inspection or network request handling, but agents can work around this for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources