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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。