Skip to main content
Glama
estebansolis

Chilipad MCP

by estebansolis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Chilipad MCP

No user-submitted related servers found.

    Related Servers

    • iaqualink-mcp

      jgonzalez007
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to monitor and control Jandy iAqualink pool and spa equipment, including device status, power toggling, temperature settings, and lighting effects.
      MIT

    • MCP Govee

      danjam
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
      9
      1
      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

    • Bond MCP Server

      madorn
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Bond Bridge smart home devices including ceiling fans, motorized shades, dimmable lights, and other RF-controlled devices. Provides comprehensive device management and control capabilities through the Bond Local API.
      10
      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

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct resources/actions (device status, water status, sleep reports, mappings, routines, automation). There is some edge overlap among status/read tools such as get_setup_status, get_device_status, check_water_status, and get_routine_status, plus identification recovery versus setup status, but descriptions provide enough separation.

    Naming Consistency5/5

    All tool names use snake_case with a predictable verb_noun or verb_object pattern. Minor verb variation like check_water_status versus get_device_status is still readable and consistent within the set.

    Tool Count5/5

    Fifteen tools is appropriate for a domain covering device discovery, status inspection, mapping, control, identification, routines, and automation recovery. Each tool appears to cover a distinct operation without obvious filler.

    Completeness4/5

    The surface covers the core lifecycle: setup, discovery, status, control, mapping, identification, routine management, and automation recovery. Minor gaps remain, such as no explicit device-claim/pairing tool or inbox acknowledgement operation, but agents can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources