Skip to main content
Glama
norman2112

bhyve-mcp

by norman2112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BHYVE_EMAILYesYour Orbit B-Hyve account email
BHYVE_PASSWORDYesYour Orbit B-Hyve account password

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_devicesA

List all B-Hyve devices (controllers, hubs, hose timers, flood sensors) on the account.

Returns device id, name, type, status, firmware, station count, battery, and connectivity. Use device IDs from this response with all other tools.

get_device_statusA

Get current status of a specific device including watering state and rain delays.

Args:
    device_id: Device ID from list_devices.
get_zone_detailsB

Get detailed info for all zones on a device.

Args:
    device_id: Device ID from list_devices.
get_programsB

List watering programs configured for a device.

Args:
    device_id: Device ID from list_devices.
get_watering_historyA

Get recent watering history for a device.

Args:
    device_id: Device ID from list_devices.
    page: Page number (default 1).
    per_page: Results per page (default 10).
start_wateringA

Start watering a specific zone for a given duration.

Safety: durations over 30 minutes require allow_extended_runtime=true.

Args:
    device_id: Device ID from list_devices.
    zone: Zone/station number (1-indexed).
    minutes: Duration in minutes (1-120).
    allow_extended_runtime: Set true to allow watering longer than 30 minutes.
stop_wateringB

Stop all active watering on a device.

Args:
    device_id: Device ID from list_devices.
enable_rain_delayA

Enable rain delay (pauses all scheduled watering).

Args:
    device_id: Device ID from list_devices.
    hours: Hours to delay (1-168, max 7 days).
disable_rain_delayA

Cancel an active rain delay.

Args:
    device_id: Device ID from list_devices.
set_device_modeA

Set device operating mode.

Args:
    device_id: Device ID from list_devices.
    mode: Operating mode — "auto" or "off".
update_programA

Update an existing watering program's configuration.

Programs must be created in the B-Hyve app first. Only modifies existing programs.

Args:
    device_id: Device ID from list_devices.
    program_id: Program ID from get_programs.
    start_times: Watering start times in HH:MM format.
    frequency: Frequency config with type (days|interval), days [0-6], interval int.
    budget: Watering budget percentage (0-200, 100 = default).
toggle_smart_wateringA

Enable or disable Smart Watering for a zone (device-wide water_sense_mode).

Args:
    device_id: Device ID from list_devices.
    zone: Zone/station number.
    enabled: True to enable, false to disable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
devices_resourceCurrent snapshot of all devices and their status.
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

ActivityStale
ResponsivenessNo issues

Resources