Skip to main content
Glama
chrischall

simplisafe-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to simplisafe-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.
      -

    • mcp-ha

      Devitek
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Home Assistant that lets you control and query your smart home through natural language via MCP clients. Provides tools for entities, devices, services, automations, scripts, history, add-ons, and system info, with read-only access by default and optional configurable write support.
      1
      MIT

    • mcp-hs4

      dmanfx
      A
      license
      B
      quality
      C
      maintenance
      MCP server for controlling HomeSeer HS4 with safe, auditable, and guarded write operations.
      63
      1
      MIT

    • nuki-mcp

      sandraschi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for controlling Nuki Smart Locks via Home Assistant, enabling lock/unlock, intercom buzzing, and battery checks.
      1
      MIT

    • shelly-mcp

      Buggy1111
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.
      2
      47
      MIT

    • simpleinout-mcp

      MSPbotsAI
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Simple In/Out APIv4, providing tools for check-in/out statuses, user and group management, and access to beacons, geofences, networks, announcements, and roles.
      15
      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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the descriptions clearly explain scope differences. Minor overlap exists between get_system/list_systems and list_locks/list_sensors, but the descriptions are specific enough to prevent serious confusion.

    Naming Consistency4/5

    Tool names consistently use a simplisafe_ prefix and snake_case, with a predictable get_/set_/list_ verb pattern. simplisafe_healthcheck is the one deviation, but the overall naming convention is still coherent and easy to follow.

    Tool Count5/5

    Ten tools is a well-scoped surface for a SimpliSafe integration, covering account/system lookup, alarm control, lock control, sensors, events, settings, PINs, and connection health. Each tool has a clear purpose and none feels redundant.

    Completeness4/5

    Core monitoring and control workflows are covered: listing systems, reading state, arming/disarming, listing sensors and locks, locking/unlocking, fetching events, viewing settings, and reading PINs. The main gaps are write operations for settings and PIN management, but common agent workflows should not hit dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources