rachio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List Rachio controllers on the account with status and zone summary. |
| 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". |
| list_zonesA | List every zone on a controller (number, name, enabled state). |
| list_schedulesB | List the stored schedule rules (watering times) on a controller. |
| start_zoneC | Run a single zone for the given number of minutes (max 180). |
| start_zonesA | Run multiple zones in sequence. Each item: {"zone": <num/name>, "minutes": }. They water one after another in the order given. |
| stop_wateringB | Stop all watering on a controller immediately (manual or scheduled). |
| set_rain_delayB | Set a rain delay in days (0 clears it, max 7). |
| run_scheduleB | Start a stored schedule rule by its id or name. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.