Skip to main content
Glama
paztek

twinkly-mcp

by paztek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to twinkly-mcp

No user-submitted related servers found.

    Related Servers

    • govee-mcp

      evefromwayback
      A
      license
      Not graded
      quality
      D
      maintenance
      A LAN-first, cloud-fallback MCP server for controlling Govee smart devices by name. It enables AI agents or MCP clients to manage lights, plugs, and appliances with commands like power, brightness, color, and scenes.
      MIT

    • Hermejia

      HuishanLi1997
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to control Xiaomi Mi Home smart devices through natural language, with support for listing devices, controlling properties, and running scenes.
      MIT

    • elgato-keylight

      butterflyskies
      A
      license
      A
      quality
      C
      maintenance
      MCP server for controlling Elgato Key Lights. Enables turning lights on/off, adjusting brightness and color temperature, applying presets, and triggering effects via Claude.
      13
      Apache 2.0
    • Home Assistant MCP Server by homeassistant-ai

      Home Assistant MCP Serverofficial

      homeassistant-ai
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      78
      4,732
      MIT

    • 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.
      -
    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.2/5.0

    Scored across 14 tools

    Disambiguation3/5

    Some tools have overlapping purposes (e.g., get_state vs get_summary, set_power vs set_mode, set_color vs set_mode), but descriptions help differentiate them by intent and use case. Most tools target a clear resource and action pair, so ambiguity is limited to a few pairs.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, set_, list_, discover_) using snake_case. No mixing of styles or vague verbs, making the naming highly predictable.

    Tool Count5/5

    14 tools is well-scoped for a Twinkly device control server, covering discovery, state, effects, movies, and various settings. The count is not excessive or thin, fitting the domain appropriately.

    Completeness4/5

    Core workflows are covered (discover, list, get state, set power/color/brightness/effects/movies). Minor gaps exist, such as no playlist selection or on/off timer control, but these are workable and do not break main use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources