Skip to main content
Glama
Sign In
mcp-server-return-to-dark-tower

mcp-server-return-to-dark-tower

by ChessMess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-return-to-dark-tower

No user-submitted related servers found.

    Related Servers

    • mcp-ble-bridge

      kumavulp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control Bluetooth Low Energy devices remotely through a WebSocket and Web Bluetooth bridge, exposing tools for vibration, suction, licking, pulsing, and status checks.
      MIT

    • 网易春风 · 心跳元力 MCP

      vmayfuture
      A
      license
      B
      quality
      C
      maintenance
      Enables natural-language control of DK-META2 devices through local BLE for vibration, linear extension, and rotation. It also supports scanning, connecting, status checks, and safe stop/disconnect operations without cloud access.
      8
      1
      MIT

    • MCP Govee

      danjam
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
      9
      1
      MIT

    • Fellow Aiden

      wardnb
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to design coffee brew profiles from bag photos, push them to a Wi-Fi-connected smart brewer, and keep a searchable library of recipes, versions, ratings, gear and tastings. Also lets assistants manage the brewer's active menu and scheduled brews, and preview, import or share brew.link profiles.
      GPL 3.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.6/5.0

    Scored across 34 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, such as controlling lights, sounds, seals, or drums, with clear differentiation between similar tools like tower_play_sound and tower_play_sound_by_name.

    Naming Consistency5/5

    All tools follow a consistent tower_verb_noun pattern in snake_case, making it easy to predict tool names and understand their functions.

    Tool Count3/5

    With 34 tools, the set is large but justified by the complexity of controlling a physical device; however, it exceeds the typical well-scoped range of 3-15 and is near the 'too many' threshold.

    Completeness5/5

    The tool set covers all essential aspects of the device lifecycle: connection, calibration, state retrieval, light and sound control, seal management, drum rotation, and monitoring. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources