rachio-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rachio-mcp Is anything watering right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| all controllers on the account, with status and zone summary |
| one-shot: online, on/paused, rain sensor & delay, what's watering now |
| zones on a controller (number, name, enabled) |
| stored schedule rules (watering times) |
| run one zone for N minutes (max 180) |
| run several zones in sequence |
| stop everything now |
| set/clear a rain delay (0–7 days) |
| start a stored schedule rule by name or id |
| 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+
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 syncConfigure
export RACHIO_API_TOKEN=your-api-tokenSee .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.pyOr 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"], withRACHIO_API_TOKENin 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
deviceargument (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 controllerLicense
MIT. Not affiliated with or endorsed by Rachio, Inc. "Rachio" is a trademark of Rachio, Inc.
Available Tools
10 toolsget_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
Scored across 10 tools
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.
Tool names follow a consistent verb_noun pattern throughout: list_*, start_*, set_*, stop_*, run_*. Even the plural start_zones follows logically from start_zone.
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.
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
Related MCP Connectors
Control your Tesla from your AI assistant - climate, charging, access, and security.
Read RemoteLock devices and guests; manage door access and physically lock or unlock doors.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each device’s supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
Ask about your IoT sensors, devices, anomalies and automations, switch outputs and log values.
1
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceEnables managing OpenSprinkler irrigation controllers via Claude Desktop, including starting/stopping stations, setting rain delays, and viewing controller status.-
- AlicenseNot gradedqualityCmaintenanceEnables natural language queries about Ambient Weather personal weather station data, including current conditions and device info.MIT
- AlicenseAqualityCmaintenanceMCP 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.248MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.1MIT