Skip to main content
Glama
Sign In
AgentSensor

AgentSensor

by arif-js
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AgentSensor

No user-submitted related servers found.

    Related Servers

    • TracePulse

      sourjya
      A
      license
      Not graded
      quality
      C
      maintenance
      Runtime feedback MCP server for AI coding agents. It watches dev server logs, parses errors, and exposes them as MCP tools so AI agents can instantly verify code changes.
      4 npm
      3
      AGPL 3.0

    • AIS Revizor

      bswvladimir-beep
      F
      license
      Not graded
      quality
      D
      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.
      -
    • fennec

      fennecofficial

      plumpslabs
      A
      license
      Not graded
      quality
      A
      maintenance
      AI-native developer observability MCP (Model Context Protocol) server that gives AI agents full-stack visibility into your development environment — browser, terminal, and processes — all in one unified interface.
      4 npm
      1
      MIT

    • Browser Runtime MCP

      MakiDevelop
      A
      license
      A
      quality
      C
      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

    • vite-plugin-mcp

      braylon-dunn
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables models to better understand a local Vite or Nuxt application by exposing development server context to AI tools. It provides a Nuxt module and a Vite plugin for adding MCP support to local dev servers.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools map to distinct stages of the debug loop: listing errors, inspecting one, verifying a fix, and manually resolving. check_fix and resolve_error both mutate error state (open->resolved), which creates slight boundary overlap, but their intent differs (automatic verification vs explicit manual closure).

    Naming Consistency4/5

    All names use snake_case with a verb_noun shape (get_runtime_errors, get_error_detail, resolve_error, check_fix). The verb choices vary a bit (get/check/resolve) but stay readable and predictable. Minor deviation in verb style keeps it from a perfect 5.

    Tool Count5/5

    Four highly focused tools cover a tight detect-inspect-verify-resolve workflow with no redundancy. Each tool clearly earns its place and the scope is well-matched to the purpose.

    Completeness4/5

    The surface covers the full lifecycle: discover errors, inspect detail, verify a fix, and mark resolved. Minor gaps exist (no way to list/dismiss already-resolved errors or mute/ignore a known error), but core agent debugging workflows are supported.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources