otolawn-mcp
Related Servers
Alternatives to otolawn-mcp
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityDmaintenanceMCP server for Hunter Hydrawise irrigation controllers, exposing the Hydrawise REST API as tools for AI agents to manage watering schedules and controller settings.-

Yeelight IoT MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables MCP clients to discover homes, areas, rooms, devices, groups, and scenes, query live state, and safely preview and execute device controls or scenes with dry-run confirmation.10Apache 2.0- FlicenseAqualityDmaintenanceQuery and control Orbit B-Hyve irrigation systems from MCP-compatible clients like Claude Code and Cursor.121-
- AlicenseBqualityDmaintenanceEnables natural language querying and control of Rachio smart irrigation controllers, including watering status, zone runs, schedules, rain delays, and standby mode.101MIT
- FlicenseNot gradedqualityFmaintenanceEnables managing OpenSprinkler irrigation controllers via Claude Desktop, including starting/stopping stations, setting rain delays, and viewing controller status.-
TDQS
Scored across 19 tools
Most tools target clearly distinct resources and actions (zones vs routines vs events vs devices). A few pairs could be momentarily confused—cancel_event vs stop_watering, and water_zone (manual) vs set_zone_watering (scheduled amount)—but the descriptions explicitly clarify the manual/scheduled distinction.
Every tool follows a consistent snake_case verb_noun pattern (list_zones, get_zone, set_zone_enabled, water_zone, cancel_event, etc.). No mixed conventions or vague verbs appear.
19 tools is on the heavier side but the domain is genuinely broad (zones, routines, events, devices, weather, messages), and each tool maps to a distinct operation. Slightly heavy but not bloated.
Zones have full lifecycle coverage (add/get/list/rename/enable/delete/set-watering) and devices/events are well covered. The main gap is routines: they can only be listed and enabled/disabled, with no create/edit, though zone-level scheduling partially compensates.