Skip to main content
Glama
norman2112

bhyve-mcp

by norman2112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bhyve-mcp

No user-submitted related servers found.

    Related Servers

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

    • acinfinity-mcp

      misterboe
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language control of AC Infinity UIS grow controllers to read tent climate, sensor data, port settings, and automations, and to modify port modes, power levels, timers, schedules, and automation rules via MCP clients like Claude or Codex.
      18
      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.
      -

    • ambient-mcp

      jrolstad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Ambient Weather REST API. Query your personal weather stations conversationally from Claude Code, Claude.ai, or any MCP-compatible client.
      1
      MIT

    • Hubitat MCP Server

      jgitta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to list, search, query, and control Hubitat home automation devices from MCP-compatible AI assistants like Claude Desktop.
      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.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing devices, getting status, controlling watering, rain delays, programs, etc. There is no overlap between tool functionalities.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., enable_rain_delay, get_device_status, start_watering). No mixing of conventions.

    Tool Count5/5

    12 tools cover the essential operations for a smart irrigation controller without being overwhelming or too sparse. The count is appropriate for the domain.

    Completeness4/5

    The tool set covers most key actions (device management, watering, rain delays, programs, history). A minor gap is the inability to create or delete programs, which is noted as requiring the app. Otherwise complete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources