Skip to main content
Glama
Schimmilab

somneo-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to somneo-mcp-server

No user-submitted related servers found.

    Related Servers

    • HueMCP

      mbruton
      A
      license
      A
      quality
      D
      maintenance
      Enables discovery and control of Philips Hue lighting devices via a local bridge using the CLIP v2 API, without any cloud dependency.
      10
      MIT

    • Chilipad MCP

      estebansolis
      A
      license
      A
      quality
      B
      maintenance
      Enables an assistant to locally discover and control supported Sleepme bed devices, check water status, adjust temperatures, retrieve Sleep Tracker reports, and manage saved routines.
      15
      MIT

    • tuya-local-mcp

      ethanj2k
      A
      license
      A
      quality
      B
      maintenance
      Enables local network control of Tuya and Smart Life smart home devices without cloud round-trips, including power, brightness, color, and raw datapoint operations.
      9
      MIT

    • alexa-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables controlling Amazon Alexa accounts through Alexa's private web API, including listing and controlling Echo speakers, Echo Shows and Fire TVs, making devices speak or announce, running routines, controlling smart-home devices and scenes, managing shopping and to-do lists, and viewing alarms, timers and reminders. Destructive actions are confirmation-gated, and arbitrary voice commands are deliberately excluded.
      38
      89 npm
      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 6 tools

    Disambiguation4/5

    Each alarm tool maps to a distinct CRUD action (list, create, update, delete) plus an on/off toggle, and raumklima is a separate sensor domain. The only slight overlap is somneo_wecker_schalten (on/off) versus somneo_wecker_setzen, which can also set the 'an' flag, but the descriptions clarify the intended split.

    Naming Consistency4/5

    Names follow a predictable somneo_<resource>_<action> pattern with German verbs (schalten, liste, setzen, anlegen, loeschen) for the alarm resource. somneo_raumklima deviates by being a bare resource noun with no action verb, a minor inconsistency.

    Tool Count5/5

    Six tools is well-scoped for a single-device controller: full alarm lifecycle plus a sensor read. Every tool earns its place with no redundancy or bloat.

    Completeness5/5

    The alarm surface covers the full lifecycle (list, create, update, delete, enable/disable), and room climate provides the environmental read. No obvious dead ends or missing operations for the stated device purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources