Ask Claude about your Indigo house in plain English, and have it check, switch and fix things for you.
Version: 3.9.1 | Author: CliveS & Claude | Needs: Indigo 2023.2 or later, Claude Code and a paid Claude account
Read the full guide — setting up, what everything means, and what to do when something goes wrong.
This plugin lets Claude, Anthropic's AI assistant, see and control your Indigo system from an ordinary conversation. You ask "which lights are on?", "turn the fan on for ten minutes" or "why didn't the bathroom light go off last night?", and Claude looks at the real state of your house, does what you asked, and reads the result back to check it worked. It gives Claude 71 tools to do that with.
- Answers questions about your house from the live state of every device, variable, trigger, schedule and action group, and from the event log, including entries older than the Indigo window shows.
- Controls your devices — on, off, brightness, colour, thermostats, fans, sprinklers and locks — by name, and can switch something on for a set time and off again.
- Writes and fixes scripts and plugins with you, saving a backup of a script before every change, then running it and reading the event log to see whether it worked.
- Finds what depends on what, so you know which triggers, schedules and action groups use a device or variable before you change or delete it.
- Checks the health of the system — devices in error, low batteries, devices that have gone quiet, plugins with an update waiting.
- Keeps a record of every change made through it, which you can print from the Plugins menu.
- Keeps each client to what you allow. Every tool is marked read, write or admin, deleting needs a setting you switch on, and you can give a phone a read-only key.
Everything goes through Indigo's own web server, behind the access key Indigo already uses, so nothing new is opened on your network. The plugin needs no API key and no extra Python packages.
| You need | Notes |
|---|---|
| Indigo 2023.2 or later | I develop and test it on Indigo 2025.2. |
| Claude Code | Anthropic's app for working with Claude on a Mac, on the Mac that runs Indigo. The plugin sets it up for you. The Claude desktop app can connect too — the guide shows how. |
| A paid Claude account | Claude Code needs one, usually a Claude Pro or Max subscription from claude.ai. If you already have one, there is nothing more to pay. |
Other plugins can add tools of their own to Claude Bridge — my Dashboards plugin does, for example.
- Go to the Releases page and download
Claude.Bridge.indigoPlugin.zip - Unzip the downloaded file — you will get
Claude Bridge.indigoPlugin - Double-click
Claude Bridge.indigoPlugin— Indigo will install it automatically
- When Indigo asks whether to enable the plugin, say yes. The plugin creates a Claude Bridge device, and sets Claude Code up to use it.
- Check the Indigo Event Log says Claude Code integration configured. If it says No bearer token available instead, Indigo has no access key yet, and the Getting started page shows how to make one.
- Quit and restart Claude Code, type
/mcp, and check indigo-mcp is listed as connected. Then ask it "which lights are on?"
The full guide goes through each step, explains every setting and menu item, and covers what to do if something does not work.
The three most recent releases, word for word. Every release before these is in the version history.
device_history and variable_history now read the SQLite file you chose.
- A custom SQLite file is followed. If you set the SQL Logger's SQLite file to another name, or to a full path, the tools still read
Logs/indigo_history.sqlite. They now work out the file the way the logger does: a name is a file in the Logs folder, and a path that starts with/is used as it stands. Thanks to Jon for spotting it.
Still 71 tools, 30 of them read-only.
device_history and variable_history now read a PostgreSQL SQL Logger.
- PostgreSQL history works. Before, the two tools read only the SQLite database, and 3.8.2 made a PostgreSQL logger give an error. Now they read the PostgreSQL database itself, with the same answers as for SQLite: rows, a summary, and for a variable the value before the window and how long each value held.
- No extra package. The tools use the PostgreSQL driver the SQL Logger plugin already carries, so Claude Bridge adds nothing to your Mac. The driver is the one the logger writes with, so a server the logger can log to is one the tools can read. It needs the SQL Logger plugin installed, which it must be for the history to exist.
- The login comes from the SQL Logger's own settings. If those are missing, or the server refuses them, Claude Bridge tries its own: the
CLAUDEBRIDGE_PG_keys inIndigoSecrets.py, then four new History database fields in the plugin's settings. A reply says which one it used. The password is never shown, in a reply or in an error. - Times are right whatever zone the server runs in. The logger's PostgreSQL table stores each time in the server's own zone with no zone label, where SQLite stores UTC. The tools convert in the database, then to your local time, and the tests check three different server zones.
- Read-only, and bounded. The connection refuses any write, a statement that runs past 15 seconds is cancelled, and a summary is cancelled after 5.
- Tested on a real PostgreSQL 16, not only a stand-in.
tests/test_history_postgres_live.pyrepeats that test on any server you point it at.
Still 71 tools, 30 of them read-only.
device_history and variable_history no longer give a wrong answer when the SQL Logger uses PostgreSQL.
- A PostgreSQL SQL Logger now gets an error, not an empty answer. The two tools read only the SQLite database. After a switch to PostgreSQL the old
indigo_history.sqlitestays in the Logs folder, and the tools read that: they said "success" with no rows, so Claude took a device that had been changing for days to be still. The plugin now reads the SQL Logger's database type first, and when it is not SQLite it says so and reads nothing. The PostgreSQL password in those settings is never read or shown. - Every answer now says when the history file was last written (
db_last_written), and warns (db_stale) when that was more than an hour ago, so an empty window cannot pass for "nothing changed".
Still 71 tools, 30 of them read-only.
Vibed into existence by CliveS, who knew what he wanted, argued until he got it, and tested it on a real house. Typed at inhuman speed by Claude (Anthropic), who mostly did as it was told.
© 2026 CliveS · MIT licence — copy it, fork it, bend it, break it, fix it, ship it. If it breaks, you get to keep both pieces.