baseline-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@baseline-mcp what are the current alarms on my controllers?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
baseline-mcp
An MCP server for the Baseline / BaseManager irrigation controller system at baselineapps.net.
Scope: read-only. Status, alarms, and reporting. No watering/control or schedule-edit endpoints are exposed.
Tools
Tool | What it returns |
| Logged-in user, access level, company, assigned controller ids. |
| Organizations this account can access (for multi-org accounts). |
| Sites and controllers across all accessible organizations, with model, firmware, subscription, and device counts. |
| Live snapshot: controller + per-zone + per-device status codes and decoded sensor readings. |
| Zone config: number, name, decoder, enabled, designed/learned flow, hydrozone agronomy. |
| Active alarms/faults, decoded (sender device + fault type). |
| Vendor maintenance banners as plain text. |
| Enumerate all devices by type (zones, flow meters, sensors, valves, pumps…), each with the |
| Watering programs with last/next start & finish, duration, water used, and assigned zones. |
| Current live reading for one device by serial — pressure (PSI), flow (water usage), moisture (%VWC), zone/valve/pump run state. |
| Modern reporting time-series for one device — historical pressure, moisture, temperature, flow, or zone runtime — with max/min/avg/median + points. |
| Legacy time-series report (water usage, runtimes, moisture, flow) as timestamp/value points. |
Core model: enumerate → live or history
The intended workflow is enumerate objects, then ask for live or historical data on one:
baseline_list_devices(orbaseline_get_programs) → each object carries areportingSn.baseline_get_live{ deviceSn }→ its current reading.baseline_get_history{ kind, deviceSn, from, to, granularity }→ its trend.
deviceSn is the same key for both: a sensor/meter serialNumber, or a zone decoderSN.
baseline_get_history uses the newer Analytics reporting API (/baseservice2/reporting/…)
and is the only source for historical pressure. baseline_get_report is the older
getData.php path, kept for water-usage/runtime aggregates.
Accounts, organizations & controllers
A controller is the primary key for every data tool; organizations (companies) are a grouping.
Some accounts can access multiple organizations and controllers. Tools that take a
controllerId resolve it in this order:
the explicit
controllerIdargument, elsethe
BASELINE_CONTROLLER_IDenv default, elsethe sole accessible controller (when there's exactly one).
If several controllers are accessible and none is specified, the tool returns the list so you
can pick one. baseline_list_companies → baseline_list_controllers enumerates everything.
Set BASELINE_COMPANY_ID to restrict enumeration to one organization, and/or
BASELINE_CONTROLLER_ID to pin a default controller.
Report types
baseline_get_report accepts: WaterUsage, ZoneRuntimes, ZonesActivity,
ControllerActivity, MoistureLevels, Temperature, FlowMeterTotals,
RainfallAccumulation, MeasuredFlow, ExpectedFlow. Dates are YYYY-MM-DD HH:mm;
resolution is daily or hourly; pass id to scope to a single zone/device.
Related MCP server: bhyve-mcp
Setup
npm install # also builds via the prepare hook
npm run build # or build explicitlyProvide credentials via environment variables (BASELINE_USERNAME, BASELINE_PASSWORD).
The server logs in lazily, caches the SID session cookie, and re-authenticates on expiry.
Register with an MCP client
Claude Code / Claude Desktop (claude_desktop_config.json or .mcp.json):
{
"mcpServers": {
"baseline": {
"command": "node",
"args": ["/absolute/path/to/baseline-mcp/dist/index.js"],
"env": {
"BASELINE_USERNAME": "your-username",
"BASELINE_PASSWORD": "your-password"
}
}
}
}Or with the Claude Code CLI:
claude mcp add baseline \
-e BASELINE_USERNAME=your-username \
-e BASELINE_PASSWORD=your-password \
-- node /absolute/path/to/baseline-mcp/dist/index.jsVerify
# Exercise the HTTP client against the live API (read-only):
BASELINE_USERNAME=... BASELINE_PASSWORD=... npm run smoke
# Exercise the MCP protocol layer (spawns the server, lists + calls tools):
BASELINE_USERNAME=... BASELINE_PASSWORD=... npm run mcp-checkNotes & caveats
Lenient HTTP parsing. Baseline returns a malformed multi-line
Content-Security-Policyheader that Node's defaultfetch/undici parser rejects. The client usesnode:httpswithinsecureHTTPParser: trueto tolerate it (browsers do the same). TLS verification stays on.Inferred codes. Status-key meanings (
VA,VP,VR, …) and alarm suffixes were inferred from observed data, not vendor docs. Decoders always include the raw code, andstatusTextis passed through verbatim. Seesrc/codes.ts.Endpoints are unofficial and may change without notice.
Project layout
src/
index.ts MCP server + tool definitions
client.ts BaselineClient: session lifecycle, JSON + report fetches
http.ts node:https transport (lenient parser)
format.ts payload-shaping helpers
codes.ts status / alarm / device code decode tables
scripts/
smoke.ts live API smoke test
mcp-check.ts MCP protocol smoke test
research/
API-REFERENCE.md API observationsAvailable Tools
12 toolsbaseline_get_alarmsGet alarms / faultsA
Active alarms and faults for a controller (valve short circuits, flow comm failures, dial-off, empty conditions, etc.), decoded with sender device and fault type.
Inputs: controllerId, includeCleared.
baseline_get_announcementsGet system announcementsB
Vendor proactive notifications (e.g. scheduled server-maintenance banners), as plain text.
Inputs: no named parameters.
baseline_get_historyGet historical metric seriesA
Modern reporting time-series for a single device. Kinds: pressure, zone, flow, moisture, temperature. This is the source for historical PRESSURE and for per-zone/flow/moisture/temperature trends. deviceSn is the device's reporting serial (from baseline_list_devices: serialNumber for sensors/meters, decoderSN for zones). Dates accept ISO-8601 or YYYY-MM-DD. Returns max/min/average/median plus per-bucket points.
Inputs: kind (required), deviceSn (required), from (required), to (required), +2 more.
baseline_get_liveGet live reading for a deviceA
Current live reading for one enumerated device, by its reporting serial (from baseline_list_devices: serialNumber, or decoderSN for a zone). Returns the decoded status and key/value readings, plus a primary value where meaningful: pressure sensor → PSI, moisture sensor → %VWC, flow meter → real-time water usage, zones/valves/pumps → run state. Pair with baseline_get_history for the same device's trend.
Inputs: deviceSn (required), controllerId.
baseline_get_programsList programs & run statsA
List watering programs for a controller with their last start/finish, duration, water used, next scheduled start/finish, and assigned zones. Sourced from the controller config.
Inputs: controllerId.
baseline_get_reportGet time-series reportA
Fetch a reporting time-series for a controller. Returns aligned timestamp/value points. Types: WaterUsage, ZoneRuntimes, ZonesActivity, ControllerActivity, MoistureLevels, Temperature, FlowMeterTotals, RainfallAccumulation, MeasuredFlow, ExpectedFlow. Dates are 'YYYY-MM-DD HH:mm'. Use id to scope to a single zone/device, omit for controller-wide.
Inputs: type (required), start (required), end (required), controllerId, +2 more.
baseline_get_statusGet live controller statusA
Live snapshot for a controller: overall status plus per-zone and per-device status codes (Running/Done/Off/Error/etc.) with decoded sensor readings.
Inputs: controllerId.
baseline_list_companiesList organizationsA
List the Baseline organizations (companies) this account can access. Use a companyId to scope baseline_list_controllers, or pin one via BASELINE_COMPANY_ID.
Inputs: no named parameters.
baseline_list_controllersList controllersA
List sites and controllers (with model, firmware, subscription, device counts) across every organization the account can access. Pass companyId to limit to one org.
Inputs: companyId.
baseline_list_devicesList all devicesA
Enumerate every device on a controller grouped by type (zones, flow meters, moisture/temperature/pressure sensors, master valves, pumps, rain gauges, event switches). Each entry includes the reportingSn to pass as deviceSn to baseline_get_history.
Inputs: controllerId.
baseline_list_zonesList zonesC
Zone configuration for a controller: number, name, decoder serial, enabled state, designed/learned flow, and hydrozone agronomy details.
Inputs: controllerId.
baseline_whoamiWho am IA
Validate the session and return the logged-in user, access level, current company, and assigned controller ids.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a unique read operation (listing, getting live data, history, etc.) with no overlaps. Tools like baseline_get_live and baseline_get_status are distinct: live gives a single device reading, status gives controller-wide snapshot.
All tools follow a consistent 'baseline_verb_noun' pattern in snake_case. Verbs are either 'get' or 'list', with 'whoami' being the only exception but still clearly readable.
With 12 tools, the server is well-scoped for an irrigation monitoring system. It covers key data types (companies, controllers, devices, zones, alarms, history, live, programs, reports, status) without overloading.
The tool set provides comprehensive read access to most data sources (alarms, history, live, programs, reports, status, device listing). Missing write operations (create, update, delete) which might be out of scope for a read-only server.
Related MCP Connectors
Read-only access to authorized SolarSENS solar plants, performance, devices, and alarms.
Read-only solar inverter monitoring (SolarEdge, Enphase, Huawei, Fronius): plants, energy, alarms.
Read-only energy market data: ISO prices, load, generation, regulatory dockets and weather.
Read weather station data, sensors, farms, fields and crop zones in FieldClimate.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides AI agents with read access to Trane Tracer SC+ building automation systems for inventory and telemetry retrieval.81MIT
- FlicenseAqualityDmaintenanceQuery and control Orbit B-Hyve irrigation systems from MCP-compatible clients like Claude Code and Cursor.121-
- AlicenseNot gradedqualityCmaintenanceReads thermostat status and controls HVAC modes, holds, schedules, comfort sensors, settings, vacations, fan runtime, and on-screen messages for a single thermostat account, hosted remotely on Cloudflare Workers with bearer-protected, stateless access.MIT
- AlicenseCqualityBmaintenanceProvides read-only access to DNSFilter's DNS security and filtering API, enabling users to query organizations, networks, policies, categories, block pages, and traffic and threat reports.57Apache 2.0