Skip to main content
Glama
rwestergren

rachio-mcp

by rwestergren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to rachio-mcp

No user-submitted related servers found.

    Related Servers

    • hydrawise-mcp

      b3nw
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Hunter Hydrawise irrigation controllers, exposing the Hydrawise REST API as tools for AI agents to manage watering schedules and controller settings.
      -

    • 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
      25 PyPI
      MIT

    • farmbot-agent

      kieranklaassen
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and CLI for controlling FarmBot hardware, enabling AI agents to manage gardening tasks through tools like gantry movement and device status monitoring. It supports executing Lua scripts and core hardware commands like homing and emergency stops via the Model Context Protocol.
      3
      MIT

    • bhyve-mcp

      norman2112
      F
      license
      A
      quality
      C
      maintenance
      Query and control Orbit B-Hyve irrigation systems from MCP-compatible clients like Claude Code and Cursor.
      12
      1
      -

    • fireboard-mcp

      benhodgson87
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Fireboard BBQ temperature monitoring. Enables querying devices, live probe temperatures, Drive fan controller status, and historical cook sessions.
      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.1/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource. Schedule tools are clearly separated into list, get, preview, CRUD, copy, run, skip, and history. Watering control tools (start, stop, pause, resume, skip) are unambiguous. Device, zone, weather, and alert tools each serve unique purposes with no overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., list_devices, get_device, create_schedule, pause_watering. There is no mixing of styles or inconsistent verb usage, making the naming predictable and easy to navigate.

    Tool Count5/5

    With 24 tools, the server covers the full scope of Rachio irrigation management: device/zone/schedule operations, real-time watering control, weather, alerts, and history. The count is well-calibrated for the domain—neither sparse nor bloated.

    Completeness5/5

    The tool set provides comprehensive CRUD for schedules, detailed device/zone info, weather data, alerts, and full watering control (start, stop, pause, resume, skip). Calendar and run history tools cover both planned and actual events. Only minor conveniences like a batch alert listing are missing, but core workflows are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources