list_devicesLABSCO SUMMARY
HomeKit without a middleman box.
Everything else in this space reaches HomeKit through something — Homebridge, Home Assistant, a cloud account. This is a Mac app talking to Apple's own framework, which is why reading device state and grabbing a camera still are as direct as flipping a switch.
What it is
A macOS app that exposes your HomeKit setup over MCP. It talks to Apple's HomeKit framework on the machine itself, so homes, rooms, accessories and cameras are reachable without a bridge in between.
What you get
- The homes on the account, the rooms in them, and the devices in each
- Current state of a device, readable before you change it
- Control across lights, switches, outlets, fans, locks, garage doors and thermostats — on and off, brightness, hue and saturation, lock and unlock, open and close
- The camera list, and a still captured from a HomeKit or Scrypted camera
- Plugins for Govee and Scrypted NVR, with device linking so a plugin device and its HomeKit twin do not appear twice
- Motion, doorbell and contact sensor events broadcast to your AI system
Requirements
macOS Sonoma or later, HomeKit devices already set up in the Apple Home app, and HomeKit access granted on first run. Install the release DMG, or build the Mac Catalyst target in Xcode after selecting your own development team — signing is deliberately left blank in the repo.
Setup effort
Build from source — git clone https://github.com/rodaddy/HomeMCPBridge.git
USE CASES
01
Turning something off without finding the right app
Name the room and the device and set it, rather than navigating a grid of tiles.
02
Checking whether you left the house unlocked
Read the current state of the locks and the garage door before deciding anything.
03
Seeing what set off a motion alert
Take a still from the camera covering that room right now.
04
Setting a scene by describing it
Dim the lights and set the colour across several devices in one instruction.
05
Taking stock of a home you just moved into
Walk the homes, rooms and devices to see what is actually connected.
15 tools
Listed in project docs. Your client may show a different list.
list_roomslist_homesget_device_statecontrol_devicelist_camerascapture_snapshotlist_motion_sensorsget_motion_statesubscribe_eventsget_pending_eventsscrypted_list_camerasscrypted_capture_snapshotscrypted_get_camera_statescrypted_set_webhook_tokenBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Requires
- macOS 14.0 (Sonoma) or later
- Xcode and an Apple development team to sign the build
- HomeKit-enabled devices configured in the Apple Home app
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/rodaddy/HomeMCPBridge.git
cd HomeMCPBridge
open HomeMCPBridge.xcodeprojIn Xcode, open the HomeMCPBridge target, go to Signing & Capabilities and select your Development Team.
Build and run with Cmd+R, choosing "My Mac (Mac Catalyst)" as the destination.
Grant HomeKit access when prompted, and keep the app running in the menu bar.
MCP Clients
Claude Code, Claude Desktop
JSON
{
"mcpServers": {
"homekit": {
"command": "/Applications/HomeMCPBridge.app/Contents/MacOS/HomeMCPBridge",
"args": []
}
}
}Change the path if your built HomeMCPBridge.app is not in /Applications — it must match where the app actually is.
