Skip to main content
Glama
rachio-mcp

rachio-mcp

by rudy325

What it does

Exposes your Rachio irrigation system to any MCP client (Claude Code, Claude Desktop, etc.) so you can ask "is anything watering right now?", "run the front lawn for 10 minutes", or "put it on a 2-day rain delay" in natural language.

Uses the Rachio public API — cloud, token-based, works from anywhere (no need to be on the same network as the controller).

Related MCP server: ambient-weather-mcp

Tools

Tool

Purpose

list_devices

all controllers on the account, with status and zone summary

get_status

one-shot: online, on/paused, rain sensor & delay, what's watering now

list_zones

zones on a controller (number, name, enabled)

list_schedules

stored schedule rules (watering times)

start_zone

run one zone for N minutes (max 180)

start_zones

run several zones in sequence

stop_watering

stop everything now

set_rain_delay

set/clear a rain delay (0–7 days)

run_schedule

start a stored schedule rule by name or id

set_device_power

take the controller out of / into standby

Zones and devices can be referenced by name or number, not just their API ids.

Requirements

  • Python 3.12+

  • uv

  • A Rachio account and an API token

Get your API token

In the Rachio mobile app: Profile → Get API Key → Copy. It's a single bearer token tied to your account — treat it like a password.

Install

git clone https://github.com/rudy325/rachio-mcp.git
cd rachio-mcp
uv sync

Configure

export RACHIO_API_TOKEN=your-api-token

See .env.example.

Register with Claude Code

claude mcp add rachio \
  --env RACHIO_API_TOKEN=your-api-token \
  -- uv --directory /path/to/rachio-mcp run server.py

Or with Claude Desktop, in claude_desktop_config.json:

{
  "mcpServers": {
    "rachio": {
      "command": "uv",
      "args": ["--directory", "/path/to/rachio-mcp", "run", "server.py"],
      "env": { "RACHIO_API_TOKEN": "your-api-token" }
    }
  }
}

Use with other clients (OpenAI, local models, etc.)

This is a standard MCP server — it speaks the open protocol over stdio and doesn't care which model or client drives it. Anything that supports MCP works:

  • OpenAI — the Agents SDK and Responses API accept MCP servers. Point them at: command: "uv", args: ["--directory", "/path/to/rachio-mcp", "run", "server.py"], with RACHIO_API_TOKEN in the environment.

  • Local / open-source models — via any MCP-capable client (Cline, Continue, LibreChat, Open WebUI, Goose, Zed, Cursor) running Ollama, Llama, Qwen, etc.

  • Any other MCP client — same stdio command as the Claude examples above.

The only requirement is a model that's competent at tool/function calling; the large hosted models and stronger local ones (Llama 3.1+, Qwen 2.5+) handle it well.

Notes

  • Multiple controllers: every tool takes an optional device argument (name or id), required only when the account has more than one controller.

  • Durations: zone runs are capped at 180 minutes and rain delays at 7 days, matching the API limits.

  • Standby: set_device_power(on=false) puts the controller in standby, pausing all scheduled watering until turned back on.

  • Rate limits: the Rachio API allows 1700 calls/day per token; these tools are all single calls, so normal use is nowhere near the limit.

How it fits together

MCP client ──stdio──> server.py ──HTTPS──> api.rach.io/1 ──> your Rachio controller

License

MIT. Not affiliated with or endorsed by Rachio, Inc. "Rachio" is a trademark of Rachio, Inc.

Available Tools

10 tools
get_statusA

Current state of a controller: online, on/paused, rain sensor/delay, and what (if anything) is watering right now. The one call for "what's my sprinkler doing".

Inputs: device.

list_devicesA

List Rachio controllers on the account with status and zone summary.

Inputs: no named parameters. Returns: result

list_schedulesB

List the stored schedule rules (watering times) on a controller.

Inputs: device. Returns: result

list_zonesA

List every zone on a controller (number, name, enabled state).

Inputs: device. Returns: result

run_scheduleB

Start a stored schedule rule by its id or name.

Inputs: schedule (required), device.

set_device_powerA

Turn a controller's automatic schedules on (standby off) or off (standby on). Turning it off pauses all scheduled watering until turned back on.

Inputs: on (required), device.

set_rain_delayB

Set a rain delay in days (0 clears it, max 7).

Inputs: days (required), device.

start_zoneC

Run a single zone for the given number of minutes (max 180).

Inputs: zone (required), minutes (required), device.

start_zonesA

Run multiple zones in sequence. Each item: {"zone": <num/name>, "minutes": }. They water one after another in the order given.

Inputs: zones (required), device.

stop_wateringB

Stop all watering on a controller immediately (manual or scheduled).

Inputs: device.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools clearly target distinct actions and resources, such as listing devices, zones, and schedules or setting rain delay. The main potential confusion is between start_zone, start_zones, and run_schedule, though descriptions clarify the differences.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout: list_*, start_*, set_*, stop_*, run_*. Even the plural start_zones follows logically from start_zone.

    Tool Count5/5

    10 tools is well-scoped for an irrigation controller server. Each tool covers a meaningful control or query action without unnecessary bloat or missing essential functionality.

    Completeness4/5

    The server covers core device management, zone control, schedule execution, status, and watering control. Minor gaps exist like detailed watering history or schedule editing, but the main local control workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      F
      maintenance
      Enables managing OpenSprinkler irrigation controllers via Claude Desktop, including starting/stopping stations, setting rain delays, and viewing controller status.
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for full control of Rachio sprinkler controllers via the reverse-engineered internal gRPC API, enabling schedule management, manual zone runs, rain delays, and weather data retrieval.
      24
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural-language control and monitoring of Rain Bird ESP-TM2 irrigation controllers over a local LAN, including starting zones, running programs, setting rain delays, and checking status.
      1
      MIT