Hubitat MCP Server
MCP server for Hubitat Elevation hubs that controls devices via the Maker API, with optional gated access to undocumented admin routes, supporting device listing, command sending, virtual device and hub variable automation for Rule Machine, and hub management features.
README
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 (/apps/api/{appId}/…). Hub management (firmware, Z-Wave mesh, backups, reboot) lives on undocumented admin routes that break across firmware updates — gated behind HUBITAT_ENABLE_ADMIN=true. Run task recon against your hub before relying on admin tools. |
| 2 | Cache + eventsocket is the scale solution | Hitting /devices/all on every call is fine under ~50 devices (default). Set HUBITAT_DEVICE_STORE=cached to hydrate once and apply ws://[hub]/eventsocket deltas (with dedupe). |
| 3 | Rule Machine has no API | You cannot list, read, or trigger rules programmatically. Levers are virtual switches and hub variables only. |
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 |
|---|---|
task setup-cursor |
~/.cursor/mcp.json |
task setup-claude-code |
claude mcp add hubitat --scope user |
task setup-claude-desktop |
Claude Desktop claude_desktop_config.json |
task setup-mcp |
All of the above |
To refresh Claude Code after .env changes: claude mcp remove hubitat then task setup-claude-code.
Tools
| Tool | Purpose |
|---|---|
hubitat_list_devices |
Paginated/filterable device list |
hubitat_get_device |
Device detail + attributes |
hubitat_get_device_commands |
Commands for a device |
hubitat_send_command |
Generic command + optional value |
hubitat_set_color |
Hex → URL-encoded setColor JSON map |
hubitat_list_virtual_devices |
Virtual switch/button candidates (Rule Machine levers) |
hubitat_get_hub_variable / hubitat_set_hub_variable |
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 |
|---|---|
hubitat_hub_info |
read |
hubitat_backup_status |
read |
hubitat_list_apps |
read |
hubitat_zwave_status |
read |
hubitat_hub_reboot |
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, or - Create a hub variable subscription and use
hubitat_set_hub_variable.
Configuration
See .env.example.
| Variable | Default | Purpose |
|---|---|---|
HUBITAT_HOST |
required | Hub IP/hostname |
HUBITAT_APP_ID |
required | Maker API app ID |
HUBITAT_ACCESS_TOKEN |
required | Maker API token |
HUBITAT_ENABLE_ADMIN |
false |
Register admin tools |
HUBITAT_POLL_CACHE_TTL_MS |
0 |
Soft TTL for polling store (0 = always fresh) |
HUBITAT_DEVICE_STORE |
polling |
polling or cached (eventsocket) |
Task reference
task --list
| Task | Purpose |
|---|---|
build / dev / start / inspect |
Build and run |
env:create / hub-check / recon |
Credentials + hub probe |
test / typecheck / check / clean |
Quality |
commit / changelog / bump |
Commitizen releases |
pre-commit / pre-commit:install |
Hooks |
setup-cursor / setup-claude-* / setup |
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}.yaml
Documents 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/mcp
Default transport remains stdio for Cursor / Claude Desktop.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.