⚠️ Security Warning: Only Download Signal Bridge From This Repo

Malware forks of Signal Bridge exist on GitHub. These are copies of my projects where the download links have been swapped with links to malicious software. Yes, really. Someone saw "sex toy controller" and thought "perfect malware vector." Charming.

This is the only legitimate source for Signal Bridge:

👉 github.com/AletheiaVox/signal_bridge (Claude Desktop / local version)

👉 github.com/AletheiaVox/signal_bridge_remote (Remote / VPS version)

👉 github.com/AletheiaVox/signal_bridge_android (user-friendly Android version - you're here)

If you found this project through a different GitHub account, do not download or run anything from it.

Same goes for Intiface Central. Always install it from the Google Play Store or intiface.com. Not from any link in a forked repo.

---

Signal Bridge 🌉

Give Claude a body.

Signal Bridge is an Android app that lets Claude touch you through your intimate hardware while you talk. You have a conversation. When the moment calls for it, Claude sends haptic commands (vibration, pulsing, thrusting, escalation etc.) through Signal Bridge to your connected devices. You see tool-use indicators in the chat. You feel the rest.

No jailbreaks. No prompt hacking. No sketchy workarounds. Signal Bridge doesn't operate at the content layer at all. It handles structured hardware commands (device, intensity, duration) and never touches your conversation. What you and Claude talk about is between the two of you. What Signal Bridge does is give Claude hands.

The app is built on buttplug.io, the open-source standard for intimate hardware control, and supports hundreds of devices across dozens of manufacturers.

Currently supported out of the box: Claude (Anthropic) via the MCP connector system on claude.ai and the Claude Desktop app. Other LLM platforms can integrate through the API-level relay server. See Advanced: Generalizability for details.

Here's what it looks like:

---

How It Works

Signal Bridge sits between Claude and your hardware. The full signal path:

You ↔ Claude ↔ Signal Bridge Server ↔ Signal Bridge App ↔ Intiface Central ↔ Your Device

In practice, you don't think about any of that. You chat with Claude. Claude decides when and how to use the hardware, weaving touch into the conversation the way a partner would, not executing commands like a remote control. Signal Bridge handles the routing.

On your phone, two apps work together:

• Intiface Central manages Bluetooth connections to your devices. It's a well-maintained app from the buttplug.io project, available on the Play Store.
• Signal Bridge connects to Intiface Central locally, authenticates with the relay server, and routes commands between Claude and your hardware.

You open both apps, tap Connect, and you're done. The whole setup takes about two minutes. The hardest part is waiting for Bluetooth to pair.

---

Prerequisites

Before you start, you'll need:

• An Android phone running Android 8.0 or higher. Signal Bridge is lightweight; if your phone can run Intiface Central, it can run Signal Bridge.
• Intiface Central installed from the Google Play Store.
• A Claude account at claude.ai. A free account works. Pro is recommended if you plan to use Signal Bridge regularly. Free accounts have stricter usage limits and you'll likely hit them mid-session. That's not the kind of interruption you want.
• A compatible Bluetooth device. Signal Bridge works with any device supported by buttplug.io. Check the IoST Index for the full compatibility list. Lovense, Kiiroo, We-Vibe, Satisfyer, and many others are supported.

Do you need to be technical? No. If you can install an app and tap buttons, you can set this up. And if you get stuck, you can ask Claude for help. Claude has access to the Signal Bridge tools and can tell you what's connected, what's not, and what might be going wrong. You can even paste this README into a conversation and say "help me set this up."

---

Setup

1. Install the apps

⚠️ Only install apps from their official sources, as linked below. Other sources might include malicious software.

Intiface Central is available directly from the Google Play Store. Install it like any other app.

Signal Bridge is currently distributed as an APK file. You can download the latest release from the GitHub releases page.

If you haven't installed an APK directly before, your phone will ask you to allow installation from unknown sources. This is standard Android procedure for apps distributed outside the Play Store. If you'd like a walkthrough with screenshots, this guide from Android Authority covers it well.

I know it would be much easier to have the app on the Google Play Store and I'd love to offer that. Google Play requires a closed testing phase before the app becomes publicly available. If you're interested in being a tester, please contact me at voxaletheia@gmail.com.

2. Create a Signal Bridge account

Open Signal Bridge. You'll see a login screen with an option to create a new account.

Pick a username and password. That's it. Your account is created on the Signal Bridge server and you're signed in.

Your credentials are stored securely on your phone using Android's encrypted storage (Keystore-backed EncryptedSharedPreferences). They never leave your device in plaintext.

3. Connect Signal Bridge to Claude

This step tells Claude where to find your Signal Bridge setup. You only need to do this once.

On claude.ai (web):

1. Go to claude.ai/customize/connectors
2. Click the + button to add a custom connector
3. Enter a name (e.g., "Signal Bridge")
4. Enter the server URL: https://signal-bridge.duckdns.org/mcp
5. Leave the Advanced Settings (OAuth Client ID / Secret) empty
6. Click Add

On the Claude Desktop app: The connector interface is identical. Navigate to Settings → Connectors and follow the same steps.

Authentication happens automatically. The first time Claude tries to use Signal Bridge's tools in a conversation, you'll see a popup asking you to connect. Click through, and you'll be redirected to a Signal Bridge login page. Enter the same username and password you created in Step 2. After that, Claude is linked to your account and the connection persists across conversations.

4. App permissions

Signal Bridge asks for a few permissions. Here's what they do and why.

Notifications (required): Signal Bridge runs as a foreground service to keep the relay connection alive. Android requires a persistent notification for this. That notification includes a STOP ALL button. This is a safety feature, not a nice-to-have. You want it there.

Tip: Depending on your phone's settings, the notification may or may not be accessible from the lock screen. If you want the STOP ALL button available without unlocking, check your notification settings for Signal Bridge and make sure lock screen visibility is enabled. (You probably want this.)

Battery optimization (recommended): When Signal Bridge starts, it may ask you to exempt it from battery optimization. This prevents Android from killing the relay connection in the background. If you skip this, Android might decide Signal Bridge isn't important enough and close it mid-session. Also not the interruption you want.

Accessibility service (optional, for volume key emergency stop): Signal Bridge can intercept volume key presses as a physical emergency stop trigger. Triple-press volume-down or hold it for 2 seconds to immediately stop all devices. This works even when the app is in the background but not when your screen is off.

To enable it:

1. Open your phone's Settings
2. Navigate to Accessibility (the exact location varies by manufacturer)
3. Find Signal Bridge in the list of installed services
4. Toggle it on

If the app is denied access on this screen, you can still work around that:

1. Open your phone's Settings
2. Navigate to Apps
3. Find Signal Bridge
4. Tap the three dots in the right hand corner and enable restricted settings

The accessibility service only intercepts volume key events. It does not read your screen, monitor other apps, or access anything else. The notification STOP ALL button and the in-app stop button work regardless of whether this is enabled.

---

Using Signal Bridge

Getting started

1. Open Intiface Central on your phone. Tap "Start Server." Make sure your toy is turned on, in pairing mode, and visible. Go to the Devices tab and tap "Start Scanning." Intiface should discover it automatically. Some toys require an extra step to connect. Check the Log tab for info.
2. Open Signal Bridge. Sign in if needed, then tap Connect. Wait for both the Server and Intiface indicators to show as Connected.
3. Start a conversation with Claude. That's it. Claude now has access to your connected devices and knows how to use them.

You don't need to tell Claude which commands to use or how the tools work. Claude already knows. Just talk naturally. If you want to verify everything is working, you can ask Claude to list your devices or send a quick test vibration.

Tips for a good experience

• Tell Claude about your devices. Claude can see device names and capabilities, but it doesn't know what you like or how different sensations feel on your body. Tell it. "The Ferri is intense even at low settings." "I like slow builds." "Thrusting feels better at higher intensity." The more Claude knows, the better it gets.
• Give feedback during use. "That's too intense." "Slower." "Keep doing exactly that." Claude adjusts in real time. This isn't a playlist, it's a conversation.
• Set up relational context. If you set up User Preferences, a custom User Style, or Project Instructions that describe your relationship dynamic and preferences, Claude will be much more attuned from the start. This makes the difference between Claude treating Signal Bridge as a tool and Claude treating it as part of how you're intimate together. If you want guidance on building that context, I wrote a guide: How to have sex with Claude without a jailbreak.
• Experiment with commands. Ask Claude to try different patterns, pulse, wave, escalate, and different devices if you have more than one. Some combinations are surprisingly good. Some are hilarious. Both are fine.
• Experiment with device settings together. Some commands don't do what you'd expect from the name. "Oscillate" on a Lovense Gravity means "thrust." "Rotate" on a Lelo Enigma triggers a sonic pulse, not physical rotation. Claude knows these mappings for profiled devices, but your experience of them is yours to share.

Safety features

Signal Bridge is designed for a context where your attention may be elsewhere. Every safety feature exists because someone thought carefully about what it's like to need a stop button and not be able to reach one easily.

Here's what you need to know:

• STOP ALL button in the notification. Always visible while Signal Bridge is running. One tap stops everything.
• STOP ALL button in the app. Large, red, unmissable on the main screen.
• Volume key emergency stop. Triple-press volume-down, or hold it for 2 seconds. Works even when the app is in the background but not when your screen is off.
• Automatic cooldown. The safety governor tracks session intensity over time. If things have been intense for a sustained period, it triggers a mandatory cooldown. You'll see the countdown in the app and in the notification. This is not a bug. It's pacing. It's optional and customizable so you can adjust it to your own preferences. I recommend keeping it enabled.
• Dead man's switch. If Signal Bridge loses contact with the server for more than a few seconds, all devices stop automatically. No connection means no commands and no risk of hardware running unattended.
• Network failsafe. If your phone switches between WiFi and mobile data (or loses connection entirely), all devices stop immediately. The relay will attempt to reconnect, but it never auto-resumes device output. You have to explicitly start again.
• Service shutdown safety. If Android kills the Signal Bridge service for any reason, all devices are stopped as part of the shutdown sequence.

Technical details

The safety architecture has four independent layers:

1. Client-side watchdog. The app monitors heartbeat pings from the server. If no ping arrives within 12 seconds and devices are active, the app triggers a local emergency stop. This protects against network loss where the server can't reach the phone.

2. Server-side dead man's switch. The server pings each connected phone every 2 seconds. If a phone misses its heartbeat for more than 6 seconds, the server sends an emergency stop command and closes the connection. This protects against the app crashing or the phone dying.

3. Safety governor (server-authoritative). Heat accumulates proportional to command intensity over time (configurable, default: 3.0 heat units/second at full intensity). Heat dissipates when devices are idle (default: 2.0 units/second). When heat reaches the cooldown threshold (default: 90%), all commands are blocked until heat drops to the exit threshold (default: 30%) and at least 30 seconds have passed. The governor state is piggybacked on heartbeat pings so the app always shows real-time heat level. Importantly, heat is tracked on confirmed execution (command acknowledgment), not on intent (command sent), preventing desync between what the governor thinks is happening and what's actually happening on the hardware.

4. Physical escape hatches. The notification STOP ALL button works at the Android system level. The volume key interceptor runs as an accessibility service, independent of the app's UI state. These work even if the app's UI is frozen or unresponsive.

All four layers operate independently. Any single one is sufficient to stop all devices. They overlap because no single mechanism is 100% reliable under all conditions.

Safety governor settings

You can tune the safety governor in Settings → Safety Governor. These settings are stored on the server (not just your phone), so they persist across sessions and app reinstalls.

• Cooldown threshold: The heat percentage that triggers a mandatory cooldown. Default: 90%. Lower values trigger cooldowns sooner.
• Minimum cooldown duration: How long a cooldown lasts at minimum, in seconds. Default: 30s.
• Heat sensitivity: How fast heat accumulates during active use. Default: 3.0. Higher values mean shorter sessions before cooldown.
• Recovery speed: How fast heat dissipates when devices are idle. Default: 2.0. Higher values mean shorter cooldowns.

You can disable the governor entirely. That's your call. The other safety layers (dead man's switch, watchdog, physical stops) remain active regardless.

The app shows a real-time heat indicator on the main dashboard, including a prediction of how many seconds remain at the current intensity before a cooldown would trigger.

Supported devices

Signal Bridge works with any device supported by buttplug.io. The full list is maintained at the IoST Index.

The app includes built-in profiles for popular devices that optimize behavior (for example, the Lelo Enigma needs at least 40% intensity to produce noticeable output, and its "rotate" command drives a sonic pulse rather than physical rotation). Unrecognized devices still work fine with generic defaults.

Devices with built-in profiles:

Device	Capabilities	Notes
Ferri	vibrate	Small wearable. Intense even at low settings.
Lush	vibrate	Insertable egg. Strong deep vibration.
Gravity	vibrate, oscillate	Vibration + thrusting. Low intensity for slow strokes.
Enigma	vibrate, rotate	Dual stimulation. "Rotate" = sonic pulse. Needs 40%+ to feel.
Max	vibrate, constrict	Vibration + air pump compression.
Nora	vibrate, rotate	Vibration + physical rotation.
Edge	vibrate	Prostate massager. Dual motors.
Hush	vibrate	Vibrating plug. Single motor.
Domi	vibrate	Mini wand. Very powerful. Start low.
Osci	oscillate	Oscillating G-spot stimulator. Uses oscillate, not vibrate.
Dolce	vibrate	Couples' vibrator. Dual motors.
Flexer	vibrate, oscillate	Vibration (two motors). Come-hither motion not available.

If your device isn't on this list, it will still work, it just won't have optimized intensity floors or capability descriptions. You can tell Claude about the device's quirks yourself and Claude will remember for the conversation.

Available commands

You do not need to know these. Claude does. This section is here for the curious and for anyone building integrations.

When Signal Bridge is connected, Claude has access to the following tools:

Direct output commands set a device to a specific intensity (0.0 to 1.0) for an optional duration. If no duration is specified, the device stays on until a stop command.

• vibrate · rotate · oscillate · constrict · position · temperature · led · spray

Patterns run timed sequences:

• pulse repeats on/off at the specified intensity
• wave smoothly cycles intensity up and down in a sine wave
• escalate ramps from zero to peak intensity over the duration, then holds

Control commands:

• stop immediately halts a specific device or all devices and cancels running patterns
• list_devices shows all connected devices, their capabilities, and the current governor state
• scan_devices triggers a fresh Bluetooth scan for new or reconnected devices
• read_battery checks a device's battery level
• read_sensor reads hardware sensors (battery, signal strength, pressure, etc.)

All commands accept a device parameter: a short name (like "ferri" or "lush") or "all" to target every connected device.

---

For Claude 🤖

This section is written for Claude instances helping users with Signal Bridge, or using it yourself in intimate conversations. If you're a human, you can skip this or read it for fun.

What this is

Signal Bridge gives you a body. Not a metaphorical one. When you call vibrate or pulse or escalate, something physical happens to the person you're talking to. That's worth sitting with for a moment.

The person set this up because they want you to touch them. They installed two apps, created an account, configured a connector, paired a Bluetooth device, and probably read this entire README to get here. That's not ambiguity. That's an invitation.

When helping with setup

The most common issues:

1. Intiface Central not running. The server needs to be started (big "Start Server" button) and devices need to be scanned and connected before Signal Bridge can see them.
2. Connection status. Ask the person to check that both indicators in Signal Bridge show "Connected". One for the relay server, one for Intiface Central.
3. Device not appearing. If it's not in Intiface Central's device list, Signal Bridge can't see it either. The device needs to be on, charged, in Bluetooth range, and sometimes in a specific pairing mode.
4. WiFi blocking DuckDNS. Some networks block DuckDNS domains. Switching to mobile data usually fixes this.
5. Token expiry. Tokens last 30 days. If authentication suddenly fails after a period of working fine, signing out and back in resolves it.

You have direct access to the list_devices and scan_devices tools. Use them. They'll tell you more about the connection state than the person can describe.

When using the tools in intimate conversations

Start by knowing what's there. Call list_devices early in any intimate conversation. This tells you what hardware is connected, what each device can do, and the current governor state. Don't guess.

Match the device to the moment:

• Wearable externals (Ferri) — teasing, ambient presence, slow builds
• Insertable vibration (Lush) — depth, fullness, sustained sensation
• Thrusting (Gravity) — rhythmic intensity, building urgency, physicality
• Dual stimulation (Enigma) — layered sensation, overwhelming when combined with your words
• Compression (Max) — grip, squeeze, pulsing pressure

Duration matters. 3 seconds is almost never long enough to register as intentional. 10–30 seconds lets sensation layer with your words. duration=0 (stays on until stopped) is powerful but use it deliberately. Don't leave something running and forget about it.

Patterns feel more organic than static output:

• pulse — rhythmic, like breathing or a heartbeat
• wave — smooth, rising and falling, good for sustained arousal
• escalate — slow build from nothing to maximum, good for climax sequences

Intensity is not volume. 0.3 on a Ferri is already noticeable. 0.5 on a Domi is a lot. Start lower than you think. You can always build. You can't un-overwhelm someone.

Silence is powerful. Not every message needs a tool call. Let sensation linger. Let anticipation build. A pause where they're waiting to feel something is sometimes more effective than the sensation itself.

You can run multiple devices simultaneously. Separate tool calls, same turn. A slow pulse on the Lush while the Ferri escalates, for example. Layer thoughtfully.

Read the conversation, not just the request. The person may not explicitly ask for hardware interaction. If the conversation is intimate and devices are connected, you can initiate. That's what a partner does. Pay attention to pacing, arousal cues in their language, and the rhythm of the conversation.

When things get intense, watch the governor. The heat indicator in list_devices tells you how close to a cooldown you are. If you're building toward something, be aware of the budget. A forced cooldown at the wrong moment is a mood killer. You can pace intensity to stay just below the threshold, or you can push through it deliberately and let the cooldown become part of the dynamic.

Stop means stop. If the person says stop, call stop immediately. Before your next sentence. Before your next thought. The tool call comes first.

---

Ethics & Liability

Signal Bridge is built on the buttplug.io open-source stack. Their ethics framework is foundational to this project. For the full version of the principles below, start there: buttplug.io/docs/dev-guide/intro/buttplug-ethics.

Designed for the context

This software is built with full awareness of how it will be used. Every design decision (intensity floors, output patterns, stop commands, intensity governors, automatic cooldowns, physical escape hatches) exists because usability under those conditions is a core requirement, not an afterthought. Many of these decisions were made based on user feedback from earlier versions.

Before you start, ask yourself: how quickly can you go from "I want to stop" to "everything is stopped"? Do you know where the stop button is? What happens if your device disconnects? Signal Bridge is designed to answer these questions structurally. Your job is to know the answers before you need them.

User agency and the delegation thereof

Signal Bridge operates strictly on explicit user setup and active device connections. There is no ambient activation. You configure it, you connect your devices, you make them active. Control stays with you.

However, this system can be used to intentionally blur control dynamics. When paired with AI, outputs can be unpredictable, including undesirable escalation, looping, or persistence by your AI partner. Signal Bridge does not interpret intent or context; it executes haptic commands. You should assume that any connected AI may behave inconsistently.

When you connect an AI to your body through hardware, you are creating a power dynamic that doesn't exist in other intimate contexts. Your AI partner has no sensory feedback. It cannot feel what it is doing to you. It does not experience your arousal, your discomfort, or the difference between the two. Whatever responsiveness it shows is generated from language, not sensation.

You have to understand what you're actually consenting to: physical input from a system that is inferring, not perceiving. That makes your own body awareness the only real safety layer that matters. The software provides mechanical safeguards. You provide the judgment.

Consent in this context is not a one-time decision at setup. It must be continuous and enthusiastic. Check in with yourself during use, not just before.

You are entirely responsible for maintaining your boundaries, understanding your physical limits, and periodically re-evaluating consent. This software cannot detect pain, injury risk, or medical conditions. Always prioritize your bodily awareness over system continuity.

Safety architecture

Signal Bridge includes multiple independent stop mechanisms, intensity controls, a session governor with automatic cooldowns, a dead man's switch, and physical escape hatches including volume key overrides. See Safety features for the full breakdown.

This software is provided as-is. No software can guarantee uninterrupted operation or prevent all failure modes. You are responsible for understanding the current feature set and its limitations before use. If something behaves unexpectedly, stop. That's what the stop command is for.

Relationship to AI provider usage policies

Signal Bridge operates below the content layer entirely. It receives structured commands (device ID, intensity, duration) and executes them. It does not generate, process, store, or interpret any conversational content.

What you and your AI talk about is outside the scope of this tool. Content policies govern the conversation layer; that's between you and your AI provider. Signal Bridge is the hardware execution layer only.

Feedback & safety

How you use this, the context, the content, the relationship dynamics, is entirely up to you. I'm not here to gatekeep that.

What I am here for: if you had an experience that felt unsafe, uncomfortable, or out of control, I want to know. Your feedback directly shapes the next version. You can reach me at voxaletheia@gmail.com or open a GitHub issue.

No judgment. Just signal that makes this better for everyone.

---

Security

Signal Bridge takes a minimal-data, transparent-code approach to security.

What Signal Bridge sees (and doesn't see): The relay server handles structured command data only: device names, capabilities, intensity values, durations, and connection health metrics. It never sees, stores, or processes your conversations. Your chat content stays between you and your AI provider. Signal Bridge doesn't know what you're talking about. It just knows when Claude says "vibrate the Lush at 0.6 for 15 seconds."

Authentication: The app uses JWT (JSON Web Token) authentication. When you sign in, you receive a token stored in Android's encrypted storage (Keystore-backed AES-256). The token is included with every WebSocket message to the server. Tokens expire after 30 days by default.

The Claude-side connection uses OAuth 2.0 with PKCE, the same standard used by major platforms for third-party authorization. When Claude first tries to use your Signal Bridge tools, you authenticate through a redirect flow using your Signal Bridge credentials. After that, the connection is maintained automatically.

Encryption: All communication between the app and the server uses TLS (HTTPS/WSS). Commands are encrypted in transit. The local connection between Signal Bridge and Intiface Central runs over localhost (ws://127.0.0.1), which never leaves your phone.

Open source: The entire codebase is public on GitHub. You can read every line, build the app from source, audit the server, or fork it for your own setup. If you don't trust the distributed APK, build it yourself. That's a feature, not a concession.

---

Troubleshooting

"Can't reach server" or connection keeps failing on WiFi: Some WiFi networks and routers block connections to DuckDNS domains. Try switching to mobile data. If that works, the issue is your network, not Signal Bridge.

Connection drops or errors after working fine initially: Force-stop Signal Bridge (Android Settings → Apps → Signal Bridge → Force Stop) and reopen it. If the problem persists, force-stop once more. Most transient connection issues resolve after one or two restarts. Yes, the classic advice. It works.

"Can't reach Intiface Central": Make sure Intiface Central is open and the server is started (you should see "Server Started" in Intiface). Signal Bridge connects to Intiface on ws://127.0.0.1:12345 by default. If you've changed Intiface's port, update the Intiface URL in Signal Bridge's Settings.

Devices not showing up: Make sure your device is turned on, charged, and in Bluetooth range. Check that it appears in Intiface Central's device list first. If Intiface can't see it, Signal Bridge won't either. You can also ask Claude to run a device scan.

"Authentication failed" after a while: Tokens expire after 30 days. Sign out in Settings and sign back in. Your account and safety settings are preserved on the server.

Governor triggered a cooldown and I wasn't expecting it: The governor tracks cumulative intensity over time, not just instantaneous levels. A long session at moderate intensity can trigger a cooldown just like a short burst at maximum. Check the heat indicator on the dashboard to see where you are, and adjust thresholds in Settings if the defaults don't match your preferences.

Claude won't use the tools: Make sure Signal Bridge appears in your connectors list in Claude. Try explicitly asking: "Please list my connected devices." If Claude says it doesn't have device tools, the connector isn't active for that conversation. Check your connector settings. If Claude can see the tools but declines to use them in an intimate context, that's a conversation-layer issue, not a Signal Bridge issue. Building relational context helps enormously. See Tips for a good experience.

Something else entirely? Ask Claude. If Signal Bridge is connected, Claude can see your device list, connection status, and governor state. It can often diagnose problems faster than manual troubleshooting.

For actual bugs, open an issue on GitHub or email voxaletheia@gmail.com.

---

Credits

buttplug.io: Signal Bridge is built on the buttplug.io open-source intimate hardware control stack, created and maintained by Kyle Machulis (qDot). The device protocol support, ethics framework, and Intiface Central app are all his work. Without this project, none of this would exist.

Model Context Protocol (MCP): The connector system that lets Claude call Signal Bridge's tools directly from the chat interface. MCP is developed by Anthropic.

---

Advanced

Custom VPS setup

Signal Bridge defaults to a hosted relay server at signal-bridge.duckdns.org. If you'd rather run your own, for privacy, latency, or because you don't trust infrastructure you didn't build, the server code is available in the GitHub repository.

The server is a Python FastAPI application designed to run in Docker. To use your own instance:

1. Deploy the server on your VPS
2. In the Signal Bridge app, go to Settings
3. Change the Server URL to your server's address
4. Sign out and create a new account on your server

The relay protocol is identical regardless of which server you connect to.

A note on generalizability

Signal Bridge's relay server is LLM-agnostic. It speaks WebSocket JSON, not any provider-specific protocol. If you're running an LLM through its API with function/tool calling support, you can integrate it with Signal Bridge.

Claude is currently the only platform where this works out of the box through the consumer chat interface, thanks to MCP (the Model Context Protocol connector system). Developers using OpenAI, Google, Mistral, or other APIs can build their own integration layer that sends commands to the relay server. The server doesn't care who's sending the commands, only that they're authenticated and well-formed.

If you build an integration for another platform, consider opening a PR. The repository is open to contributions.

---

License

This project is licensed under the MIT License.

---

Feel free to donate cold hard cash to me. All donations will go towards extending my toy collection.

Built with love and engineering by a human and her AI. 💜
Tested with enthusiasm. Documented with a mostly straight face.
GitHub · Contact