One tiny server per board. Everything else talks to it.
It starts with an agent, a small, zero-fuss server you drop on a Raspberry Pi or a $6 Pico W. It exposes every GPIO pin over a clean REST API: read, write, pulse, watch. From there, the rest of the family builds up: smart-home bridges make your pins show up in Apple Home and Google Home, an MCP server hands the keys to AI assistants like Claude, and webhooks push every change back to you in real time. Each piece is a small, standalone, MIT-licensed project, use one, or use them all.
Agents: the muscle
A single-file REST server on the Pi or Pico W drives the pins: outputs, inputs, pull-ups, pulses with auto-revert, reversed relay logic, and webhooks on every change. Same API on both boards, clients never care which one answered.
Bridges: the home
Matter and native-HomeKit bridges declare your devices in one JSON file, lights, locks, garage doors, valves, sensors, buttons, and drive them through the agents' API. Pair once, control from your phone, your watch, or "Hey Siri".
MCP: the brain
A zero-dependency Model Context Protocol server exposes the whole GPIO surface as tools. Ask Claude to scan your LAN for agents, flip a relay, or watch a door sensor, in plain language.