Skip to main content
Glama
pikerr

SprutHub MCP Server

by pikerr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SprutHub MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Home Assistant Server

      nikolovnet
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to control Home Assistant devices, including lights, switches, and climate devices, through natural language commands.
      -

    • Larnitech MCP

      mpopovych-thinkhome
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to smart-home controllers to read device snapshots, watch live state changes, look up type-specific documentation and known vendor quirks, save and compare data snapshots, and perform guarded two-phase writes for lights, climate, blinds, sensors and meters. Writes stay disabled until explicitly enabled, are previewed and token-confirmed before execution, and report what actually landed on the device.
      27 PyPI
      1
      MIT

    • MCP-HASS

      max-rousseau
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Home Assistant, enabling them to discover and control smart home entities, services, areas, devices, and cameras via the Model Context Protocol.
      4
      BSD 3-Clause

    • scrypted-mcp

      hooptiej
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to list, inspect, snapshot, and control Scrypted home-automation/NVR devices such as switches, locks, and cameras through natural language.
      49 npm
      MIT

    • Home Assistant MCP Server

      mjrestivo16
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.
      1
      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

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (list_rooms, get_device, set_characteristic, restart_hub, etc.), so an agent can pick the right one. Minor overlap exists: sprut_get_summary aggregates hub info, rooms, devices, extensions, and scenarios already covered by dedicated list tools, and sprut_set_switch is a convenience wrapper over sprut_set_characteristic for switch services.

    Naming Consistency5/5

    Every tool uses the sprut_ prefix followed by a consistent verb_noun pattern (list_catalog, get_device, set_switch, run_scenario, create_room, update_room, delete_room). Naming is uniform and predictable across the whole set.

    Tool Count4/5

    18 tools is slightly on the heavy side but each maps to a real smart-home operation, so it is not bloated. It earns most of its places, with only sprut_get_summary arguably redundant against the individual list tools.

    Completeness4/5

    Rooms have full CRUD, devices have list/get/set coverage, and telemetry, logs, catalog, scenarios, and extensions are all reachable. Gaps remain around scenario lifecycle (list/run only, no create/update/delete) and extensions (read-only), but agents can cover the core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources