Skip to main content
Glama

Related Servers

Alternatives to Flutter Lamp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a stdio JSON-RPC tool surface that lets AI agents control running Flutter and Dart apps — starting, stopping, reloading, and hot-restarting sessions, reading logs, running doctor/list/tinker checks, and invoking plugin-contributed tools. It gives agents one shared protocol instead of ad hoc shell scripts.
      2
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to remotely debug CarDeck devices over a WebSocket bridge: tail and fetch complete device logs, send whitelisted connection commands, display on-device notifications, prompt users to reproduce issues, and push APK updates for one-tap reinstall.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect a running VS Code webview or extension host in real time, exposing DOM, console, state-store, performance, and message-traffic data over a stdio connection. Tool activation is config-driven, so MobX, Redux, Zustand, or Apollo store tools and backend-side tools appear only when the corresponding adapters are wired up.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Connects AI agents to live observability stacks including Sentry, GitHub, Vercel, Better Stack, and Cloudflare, enabling end-to-end incident investigation, deployment correlation, root cause analysis, and regression triage.
      14
      MIT

    TDQS

    A3.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    Each tool targets a distinct aspect of runtime debugging (logs, exceptions, frames, network, memory, etc.) with minimal overlap. While runtime_health aggregates several get_* tools, its purpose is clearly differentiated from runtime_status and the raw data collectors. Descriptions are detailed enough to guide correct selection.

    Naming Consistency4/5

    All tools use lower_snake_case, but the verb_noun pattern is not fully consistent: many use get_ prefix, while others are noun phrases (runtime_status, runtime_health) or phrases (what_changed). Still, the casing and readability are consistent throughout.

    Tool Count3/5

    At 22 tools, the set is on the heavy side for the stated scope, though each tool has a clear role. This falls into the borderline '16-25 feels heavy' range, as some raw data tools could potentially be consolidated.

    Completeness4/5

    The server covers connection, raw data collection, multi-dimensional diagnostics, export, and capabilities, forming a nearly complete lifecycle for runtime observation. Missing only advanced interactions like hot reload or CPU profiling, which are noted as intentional limitations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues