Hubitat MCP Server
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., "@Hubitat MCP Server turn on the living room lights"
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.
Hubitat MCP Server
MCP server for Hubitat Elevation hubs. Control devices through the documented Maker API, with optional gated access to undocumented local admin routes.
Design claims
These constraints drive the architecture:
# | Claim | Implication |
1 | Two API surfaces; only Maker API is supported | First-class tools use Maker API ( |
2 | Cache + eventsocket is the scale solution | Hitting |
3 | Rule Machine has no API | You cannot list, read, or trigger rules programmatically. Levers are virtual switches and hub variables only. |
Related MCP server: mcp-hs4
Quick start
Install the Maker API app on your hub, authorize the devices you want exposed, copy the app ID and access token.
Clone this repo and configure:
task env:create
# edit .env — HUBITAT_HOST, HUBITAT_APP_ID, HUBITAT_ACCESS_TOKEN
task setup # build + hub-check + MCP client registration (when credentials are set)Restart Claude Desktop and/or reload MCP in Cursor.
Optional:
task inspectfor the MCP Inspector UI.
Maker API setup
Hubitat UI → Apps → Add Built-In App → Maker API
Select devices (or allow all)
Copy local URLs; note
apps/api/<APP_ID>/…?access_token=<TOKEN>
MCP clients
Task | Target |
|
|
|
|
| Claude Desktop |
| All of the above |
To refresh Claude Code after .env changes: claude mcp remove hubitat then task setup-claude-code.
Tools
Tool | Purpose |
| Paginated/filterable device list |
| Device detail + attributes |
| Commands for a device |
| Generic command + optional value |
| Hex → URL-encoded |
| Virtual switch/button candidates (Rule Machine levers) |
| Hub variables (admin routes; firmware-sensitive) |
Admin plane (HUBITAT_ENABLE_ADMIN=true)
Undocumented and firmware-sensitive. Read tools first; hubitat_hub_reboot requires confirm=true.
Tool | Risk |
| read |
| read |
| read |
| read |
| destructive |
Resources
hubitat://capabilities— static capability → common commands index
Automating Rule Machine
Rule Machine has no API. To drive rules from this server:
Create a virtual switch (or button) and subscribe a rule to it, then
hubitat_send_commandwithon/off/push, orCreate a hub variable subscription and use
hubitat_set_hub_variable.
Configuration
See .env.example.
Variable | Default | Purpose |
| required | Hub IP/hostname |
| required | Maker API app ID |
| required | Maker API token |
|
| Register admin tools |
|
| Soft TTL for polling store ( |
|
|
|
Task reference
task --listTask | Purpose |
| Build and run |
| Credentials + hub probe |
| Quality |
| Commitizen releases |
| Hooks |
| MCP clients |
Prefer task commit for conventional commits. task bump updates package.json, changelog, and tags v*.
Recon (Phase 0)
task recon # writes docs/recon-{firmware}.yamlDocuments Maker API size, EventSocket samples, and which admin routes return JSON vs HTML/404 on your firmware.
Streamable HTTP (optional)
npm install express
npm run build
node dist/index.js --http :3000
# POST http://localhost:3000/mcpDefault transport remains stdio for Cursor / Claude Desktop.
License
MIT
Available Tools
8 toolshubitat_get_deviceGet Hubitat deviceARead-onlyIdempotent
Get a single device's details and current attributes from Maker API.
Use when: you need current state (switch, level, battery, etc.). Do NOT use when: you only need the list of IDs (use hubitat_list_devices).
Inputs: device_id (required). Returns: id, name, room, type, +3 more
hubitat_get_device_commandsGet device commandsARead-onlyIdempotent
List commands available for a device via Maker API. Prefer this over guessing command names.
Use when: before hubitat_send_command to confirm the command exists. Do NOT use when: sending a known simple Switch on/off.
Inputs: device_id (required). Returns: commands, device_id
hubitat_get_hub_variableGet hub variableARead-onlyIdempotent
Read a Hubitat hub variable (admin route; firmware-sensitive). Hub variables are one of two Rule Machine levers (with virtual switches).
Use when: reading a variable that rules subscribe to. Do NOT use when: controlling a device attribute (use hubitat_get_device).
Inputs: name (required). Returns: name, type, value
hubitat_list_devicesList Hubitat devicesARead-onlyIdempotent
List devices authorized in Maker API. Returns id, name, label, room, and capabilities summary.
Use when: discovering devices or finding an ID before send_command. Do NOT use when: you already know the device ID (use hubitat_get_device). Note: Rule Machine rules cannot be listed — only devices Maker API can see.
Inputs: limit, query, offset. Returns: total, devices, has_more, next_offset
hubitat_list_virtual_devicesList virtual devicesARead-onlyIdempotent
List devices that look like virtual switches/buttons (Rule Machine levers). Rule Machine has no API — flip a virtual switch or set a hub variable to trigger rules.
Use when: finding a virtual switch to drive Rule Machine. Do NOT use when: controlling physical devices (use hubitat_list_devices).
Inputs: limit, query, offset. Returns: total, devices, has_more, next_offset
hubitat_send_commandSend device commandA
Send a generic Maker API command to a device: /devices/{id}/{command}[/{value}].
Use when: turning devices on/off, setLevel, lock, etc. Do NOT use when: setting color from hex — use hubitat_set_color instead. Validates the command exists via /commands before sending.
Inputs: command (required), device_id (required), value. Returns: value, device, command, device_id
hubitat_set_colorSet device color (hex)AIdempotent
Set a ColorControl device color from a hex string. Builds the URL-encoded JSON map Maker API expects (including Hubitat's hex extension). Nobody constructs this by hand correctly.
Use when: setting bulb color from #RRGGBB or RRGGBB. Do NOT use when: only changing level or on/off.
Inputs: hex (required), device_id (required). Returns: hex, device, device_id
hubitat_set_hub_variableSet hub variableAIdempotent
Write a Hubitat hub variable (admin route; firmware-sensitive). Triggers Rule Machine subscriptions on that variable.
Use when: automating Rule Machine without a virtual switch. Do NOT use when: sending a device command (use hubitat_send_command).
Inputs: name (required), value (required). Returns: name, value
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Every tool targets a distinct resource (hub variable vs device) and action (list/get/send/set), and the descriptions explicitly provide 'Do NOT use when' guidance to steer agents away from wrong choices. The get vs list vs send tools are clearly separated by their 'Use when'/'Do NOT use when' annotations, leaving no realistic ambiguity.
The naming follows a consistent hubitat_verb_noun pattern (hubitat_list_devices, hubitat_get_device, hubitat_send_command). Minor deviations: 'hubitat_list_virtual_devices' reads more as an adjective-modifier than a pure noun, and set_color/send_command/hub_variable all mix nouns, but the pattern is mostly uniform with one verb-noun structure throughout.
8 tools is a well-scoped count for a home-automation hub server. Each pair (list/get, get/send, get_device_commands/send_command, list/get hub_variable) earns its place, and the set covers discovery, control, color, and rule-machine levers without bloat.
The surface covers device discovery, state querying, command listing, generic command sending, and color setting, plus virtual-switch and hub-variable rule triggers. Minor gaps: there's no tool for device detail beyond get_device or updating device config, but the core workflows (discover, query, control, trigger) are all covered with no dead-end operations.
Maintenance
Related MCP Connectors
MCP server wrapping the Tesla Fleet API and TeslaMate API
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.66182 npmMIT
- AlicenseBqualityDmaintenanceMCP server for controlling HomeSeer HS4 with safe, auditable, and guarded write operations.631MIT
- AlicenseAqualityBmaintenanceMCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.47MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for controlling Somfy TaHoma devices locally via the box's API, without cloud dependency.-