Skip to main content
Glama
jonfishr

tronbyt-mcp

by jonfishr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tronbyt-mcp

No user-submitted related servers found.

    Related Servers

    • pixoo-mcp-server

      cyanheads
      A
      license
      A
      quality
      A
      maintenance
      Enables programmatic control of Divoom Pixoo LED matrices to display layered pixel art, animations, and hardware-rendered scrolling text. Users can compose complex visual scenes, push images, and manage device settings like brightness and channels through an LLM.
      7
      847 npm
      9
      Apache 2.0

    • LED Display Server

      fabienhamot
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for controlling LED displays via MQTT. It enables AI agents to list devices and send text, images, colors, or clear commands with authentication and permission checks.
      -

    • vestaboard-mcp

      ykhli
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to display messages on a Vestaboard via text or board mode with color and symbol support.
      11
      -

    • mcp-server-awtrix

      klodnickik
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control and display real-time notifications, telemetry, and custom apps on Ulanzi TC001 and compatible pixel clocks running Awtrix Light, including device management and declarative YAML-based metric polling.
      6
      MIT

    • ulanzi-mcp

      Jelloeater
      A
      license
      A
      quality
      C
      maintenance
      MCP server and CLI for controlling Ulanzi TC001 Smart Pixel Clock via AWTRIX3 HTTP API. Enables power, brightness, notifications, and more from AI assistants.
      20
      2
      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 tool targets a distinct action: device management, installation management, or content pushing. The three push tools are clearly separated by input type (app, image, text), and there is no overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., list_devices, push_image). The verbs are appropriate and uniform, making the set predictable.

    Tool Count5/5

    9 tools is well-scoped for managing Tronbyt devices: 3 for device settings, 3 for installations, and 3 for pushing content. No redundant or missing tools at this scale.

    Completeness4/5

    Covers core workflows: device listing/update/reboot, installation CRUD (with push_app creating installations implicitly), and content push. Minor gaps: no device creation/deletion or single device retrieval, but these are acceptable given the assumed external device management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources