Skip to main content
Glama
bricelancasterwcp-sudo

Sensorium

by bricelancasterwcp-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Sensorium

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • backscroll

      soren-achebe
      A
      license
      A
      quality
      A
      maintenance
      Records your terminal sessions per command (PTY + OSC 133) into local SQLite, so AI agents can search, retrieve, and diff what commands actually printed. Secret redaction is applied by default to everything served over MCP.
      4
      7
      MIT

    • kmp-mcp

      underpass-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a local stdio MCP server that gives AI coding agents a typed, temporal, evidence-backed memory on embedded SQLite, letting them record decisions and constraints, ask why something happened, navigate memory by time, trace proof paths between refs, and export or supersede stored state without rewriting it. It also exposes read-only ChronoLoom view tools so a person and their agent can steer the same multidimensional memory view by semantic intent rather than raw coordinates.
      Apache 2.0

    • SuperBased Observer

      superbasedapp
      F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      48
      -

    • mcp-agent-trace-inspector

      dbsectrainer
      A
      license
      A
      quality
      B
      maintenance
      Enables local-first observability for MCP agent workflows by recording tool calls, prompts, latency, and token usage in a local SQLite database, and provides tools for inspecting, comparing, exporting, and generating dashboards from traces.
      13
      23 npm
      MIT

    • vigilante

      retamayo
      A
      license
      Not graded
      quality
      D
      maintenance
      Records runtime events from any app via zero-code instrumentation and exposes them to LLMs through MCP for autonomous debugging.
      6 npm
      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

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each of the nine tools owns a distinct slice of the trace-analysis workflow: run listing, run summary, call-tree navigation, frame detail, event search, exception classification, value/object provenance, predicate evaluation, and run comparison. Even close neighbors like tree/frame and grep/exceptions are cleanly separated by granularity and purpose. An agent should rarely misselect.

    Naming Consistency4/5

    All tool names are concise lowercase single-word commands, so the naming style is predictable and visually consistent. The only minor deviation is a mix of nouns/verb forms like info, tree, frame vs. grep, watch, diff, but there is no mixed casing or chaotic variation. This is a small style inconsistency rather than a real usability problem.

    Tool Count5/5

    Nine tools is an ideal scope for a specialized trace-analysis server: broad enough to cover the main investigative workflows, yet small enough that every command has a clear role. It is comfortably within the well-scoped range and does not feel over- or under-built.

    Completeness5/5

    The tool surface covers the full analytical lifecycle: discovering runs, reading summaries, exploring call trees and frames, searching events, classifying exceptions, tracing value/object provenance, evaluating predicates, and diffing two runs. The tools explicitly reference each other's outputs such as frame ids and event ids, enabling iterative investigation without dead ends. A raw event timeline is absent, but grep, tree, and exceptions cover that need effectively.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources