Skip to main content
Glama
DmitriyAlergant

otolawn-mcp

by DmitriyAlergant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to otolawn-mcp

No user-submitted related servers found.

    Related Servers

    • rachio-mcp

      rwestergren
      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
      7
      MIT

    • 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.
      -

    • bhyve-mcp

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

    • rachio-mcp

      rudy325
      A
      license
      B
      quality
      C
      maintenance
      Enables natural language querying and control of Rachio smart irrigation controllers, including watering status, zone runs, schedules, rain delays, and standby mode.
      10
      1
      MIT

    • opensprinkler-mcp

      Lumeo-sd
      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.
      -

    • zont-mcp

      danilmolkov
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients such as Claude to read the state of ZONT / Mega SX devices and control them, covering security arming, sirens, engine blocking, remote start, thermostats, custom commands, device management, event and sensor history, and data archives.
      12
      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

    A3.5/5.0

    Scored across 19 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources