homekit-cli
An MCP server that provides tools for inspecting and controlling Apple HomeKit accessories, scenes, automations, and more via the HomeClaw app, enabling natural language interaction with your smart home.
README
homekit-cli
homekit-cli is a TypeScript CLI and MCP server for inspecting and operating Apple HomeKit through the installed HomeClaw app.
HomeClaw owns Apple’s HomeKit entitlement, HomeKit permission prompt, and native HMHomeManager access. This package owns the agent-facing surface: Incur command groups, schemas, MCP tools, safety gates, docs, and npx skills workflow guidance.
Why the CLI?
Apple HomeKit access is entitlement-gated. A normal Node process cannot directly use HMHomeManager, prompt for HomeKit permission, or read the Home database. homekit-cli keeps Node on the agent/tooling side and talks to HomeClaw over its local Unix socket.
That means a signed App Store or TestFlight app is a hard prerequisite. Install HomeClaw from the Mac App Store, launch it once, and approve HomeKit access before running npx homekit-cli or the global homekit binary.
HomeClaw also bundles its own CLI and MCP server. Skip setup for those bundled surfaces; this repo provides the documented homekit CLI, MCP server, schemas, and external npx skills workflow.
Architecture
flowchart LR
User["User or agent"] --> CLI["homekit CLI"]
CLI --> Commands["Incur command tree"]
Commands --> Socket["HomeClaw Unix socket"]
Socket --> HomeClaw["HomeClaw.app"]
HomeClaw --> HomeKit["Apple HomeKit"]
Commands --> MCP["MCP server"]
Quick Start
Install and launch HomeClaw first, then approve HomeKit permission in HomeClaw. Do not configure HomeClaw's bundled CLI or MCP server.
Run without installing globally:
npx -y homekit-cli bridge setup --format json
npx -y homekit-cli status --format json
Or install globally:
npm i -g homekit-cli
homekit bridge setup --format json
homekit status --format json
Run as MCP without a global install:
npx -y homekit-cli --mcp
Install the published workflow skill:
npx skills add l3wi/homekit-cli --skill homekit
Development
Run from a local checkout:
bun install
bun run build
node dist/bin.js bridge setup --format json
node dist/bin.js status --format json
Run locally:
bun run dev -- --help
Run as MCP:
node dist/bin.js --mcp
Install the repo-local skill during development:
npx skills add ./skills --skill homekit --copy -y
CLI/MCP Surface
| Area | Commands | Write gate |
|---|---|---|
| Status | status |
read-only |
| Homes | homes list |
read-only |
| Rooms | rooms list, rooms create, rooms rename, rooms remove, rooms assign |
--allow-mutation |
| Accessories | accessories list, accessories get, accessories search, accessories control, accessories remove |
--allow-actuation / --allow-mutation |
| Scenes | scenes list, scenes get, scenes trigger, scenes import, scenes update, scenes delete |
--allow-actuation / --allow-mutation |
| Automations | automations list, automations get, automations create, automations create-time, automations delete, automations enable, automations disable, automations rewire, automations add-condition |
--allow-mutation |
| Zones | zones list, zones create, zones remove, zones add-room, zones remove-room |
--allow-mutation |
| Rename | rename |
--allow-mutation |
| Events | events list |
read-only |
| Device map | device-map |
read-only |
| Webhooks | webhooks status, webhooks setup, webhooks test, webhooks reset, webhooks log, webhooks log-stats, webhooks purge-log |
setup/reset/purge require mutation |
| Triggers | triggers list, triggers add, triggers update, triggers remove |
mutations require --allow-mutation |
| Provider | bridge setup, bridge status, bridge launch, bridge stop, bridge logs |
provider-specific |
control/set style operations remain intentionally explicit. No wildcard writes are supported.
Configuration
| Variable | Purpose |
|---|---|
HOMEKIT_SOCKET_PATH |
Optional HomeClaw socket override. |
HOMEKIT_USE_LEGACY_TMP_SOCKET=1 |
Use /tmp/homeclaw.sock instead of the App Group socket. |
HOMEKIT_MCP_PROFILE |
Operator label for read/write MCP profiles. Safety gates still apply. |
Default socket path:
~/Library/Group Containers/group.com.shahine.homeclaw/homeclaw.sock
Signing, notarization, provisioning profiles, app groups, and native release scripts do not live on main.
If HomeClaw is not installed or not running, the CLI exits with install guidance, the expected socket path, and the App Store link.
Project Structure
Project structure:
src/ CLI, command groups, HomeClaw socket client helpers
test/ Vitest tests
docs/ architecture, command, MCP, safety, and runbook docs
examples/ MCP/config examples
skills/homekit/ external npx-skills package
Useful commands:
bun install
bun run typecheck
bun run test
bun run lint
bun run build
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.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
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.