Skip to main content
Glama
Buggy1111

shelly-mcp

by Buggy1111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to shelly-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-tahoma

      pierresouchay
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling Somfy TaHoma devices locally via the box's API, without cloud dependency.
      -

    • hass-mcp-server

      jarahkon
      A
      license
      B
      quality
      C
      maintenance
      MCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.
      66
      113 npm
      MIT

    • Hubitat MCP Server

      solaegis
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Hubitat Elevation hubs that controls devices via the Maker API, with optional gated access to undocumented admin routes, supporting device listing, command sending, virtual device and hub variable automation for Rule Machine, and hub management features.
      8
      MIT

    • 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
    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 47 tools

    Disambiguation5/5

    Each tool targets a distinct operation on a specific resource (e.g., switch, light, cover, KVS, scene, script). Actions like set, toggle, get, list, create, delete are separated per domain, and RPC read vs write are clearly divided. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'shelly_' + domain + verb (e.g., shelly_kvs_get, shelly_switch_set, shelly_scene_create). Verbs are uniform (set, get, list, create, update, delete, run, etc.) and the naming is predictable and clear.

    Tool Count4/5

    With 47 tools, the server covers a wide range of Shelly device operations (KVS, switches, lights, covers, energy, scenes, schedules, scripts, system, webhooks, etc.). While large, each tool serves a distinct purpose and the count reflects the complexity of managing Shelly devices. Slight reduction could be possible but overall appropriate.

    Completeness5/5

    The tool set provides full CRUD-like coverage for each subsystem: KVS (get, list, set, delete), switches/light/cover (set, toggle, move), scenes (list, get, create, run, delete), schedules (list, create, update, delete), scripts (list, get_code, create, put_code, start, stop, eval, delete), virtual components, webhooks, and system operations. No obvious gaps are apparent for typical Shelly management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources