Skip to main content
Glama
JediLuke

BeamScope MCP

by JediLuke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to BeamScope MCP

No user-submitted related servers found.

    Related Servers

    • LiveTap by livetap

      LiveTapofficial

      livetap
      A
      license
      Not graded
      quality
      D
      maintenance
      LiveTap connects live data streams (MQTT, WebSocket, file tailing) to AI coding agents, enabling real-time monitoring and alerting through natural language.
      13 npm
      9
      MIT

    • SuperDev

      Xsxdot
      A
      license
      C
      quality
      A
      maintenance
      SuperDev is a local-first desktop app + MCP server that gives AI coding agents (Claude Code, Codex, Cursor — anything MCP-compatible) access to the runtime: live and historical logs across services, breakpoints in already-running processes (same PID, no restart), real browser control, and DAG deploy pipelines — with human approval and an audit trail on protected writes.
      79
      1
      Apache 2.0

    • AIS Revizor

      bswvladimir-beep
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.
      -
    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

    A4.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with explicit 'WHEN TO USE' and 'NOT FOR' guidance. Overlapping concepts like process info/state/dictionary are precisely differentiated, and project_eval is positioned as a fallback with clear directives to prefer specific tools.

    Naming Consistency4/5

    Tool names are mostly lowercase snake_case and follow a verb-first pattern like get_*, list_*, inspect_*, recompile, reload, trace_calls, stop_trace. Minor deviations include xref_callers and project_eval, which are less conventional in order but still readable and consistent in style.

    Tool Count3/5

    20 tools is within the heavy range (16-25) and might feel overwhelming. However, the server covers a broad domain (logs, processes, ETS, supervision, tracing, compilation, docs, eval), so the count is defensible. Still, it is on the higher end and could benefit from consolidation.

    Completeness5/5

    The toolset provides comprehensive coverage for debugging a running BEAM application: connection, logs, system stats, process introspection, ETS inspection, supervision tree, app config, compilation, tracing, docs, xref, and a general eval fallback. No critical dead ends exist; gaps can be filled via project_eval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources