How aletheiavox/signal_bridge works
Signal Bridge is a local MCP server that exposes Claude tool calls for controlling intimate devices through Intiface Central and the Buttplug protocol. The main workflow is Claude tool request → connection and safety checks → device command or managed pattern → hardware. The sampled source shows the controller, safety governor, device-profile loading, and command/pattern behavior; the README documents the Claude and Intiface integrations. Other README-listed tools are grouped rather than mapped individually because their implementations were not sampled.
Main entry points: signal_bridge_mcp.py Device controller · devices.json Device registry
Components 10
MCP interface
- MCP server
signal_bridge_mcp.py - Control tools
signal_bridge_mcp.py
Device control
- Device controller
signal_bridge_mcp.py - Patterns and timers
signal_bridge_mcp.py
Safety and profiles
- Device profiles
signal_bridge_mcp.py - Device registry
devices.json - Safety governor
signal_bridge_mcp.py
Other components
- Claude Desktop
- Intiface Central
- Connected devices
Connections 10
- Claude Desktop → MCP server: invokes tools
README.md - MCP server → Control tools: exposes
README.md - Control tools → Safety governor: checks safety
signal_bridge_mcp.py - Control tools → Device controller: sends commands
signal_bridge_mcp.py - Control tools → Patterns and timers: starts patterns
signal_bridge_mcp.py - Device registry → Device profiles: loads profiles
signal_bridge_mcp.py - Device controller → Device profiles: uses profiles
signal_bridge_mcp.py - Device controller → Intiface Central: connects and scans
README.md - Device controller → Connected devices: sends output
signal_bridge_mcp.py - Patterns and timers → Device controller: sends pattern output
signal_bridge_mcp.py