Skip to main content
Glama
klodnickik

mcp-server-awtrix

by klodnickik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-server-awtrix

No user-submitted related servers found.

    Related Servers

    • 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
    • mcp-divoom-lan by DivoomDevelop

      mcp-divoom-lanofficial

      DivoomDevelop
      A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to control Divoom LAN devices, including watchface management, brightness adjustment, and screen control through natural language.
      18
      52 npm
      5
      MIT

    • 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.
      8
      1,264 npm
      9
      Apache 2.0
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: app mutation, instant notification, device state query, settings, and safe preview. notify and test_render are clearly separated by side effects, while upsert_app vs notify is distinguished by persistence and priority.

    Naming Consistency4/5

    All tools share the awtrix_ prefix and use snake_case with a mostly verb_noun pattern. awtrix_notify is a minor outlier because it lacks an explicit object, but the overall naming is still predictable and readable.

    Tool Count5/5

    Six tools cover a focused display-management scope without redundancy. The count is well within the ideal range, and each tool serves a meaningful purpose.

    Completeness4/5

    The set covers app create/update/delete, notifications, settings, device state, and safe payload testing. Missing explicit list/get app endpoints are minor gaps that agents can partially work around using the existing app and state tools.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources