Signal Bridge Android

⚠️ 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 AI a body.

Signal Bridge is an Android app that lets your AI touch you through your intimate hardware while you talk. You have a conversation. When the moment calls for it, your AI 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 your AI talk about is between the two of you. What Signal Bridge does is give your AI hands (or other body parts).

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), GPT (OpenAI) and Grok (xAI) via their respective connector systems in the consumer chat interface and the Android apps. Other LLM platforms can integrate through the API-level relay server. See [Advanced: Generalizability](#a-note-on-generalizability) for details.

Here's what it looks like:

---

How It Works

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

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

In practice, you don't think about any of that. You chat with your AI. Your AI 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 your AI 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.
• An AI account. A free account works for Claude and GPT, Grok needs a paid account to use connectors.
• 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 your AI for help. Your AI 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](mailto: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. Remember your username and password, you will be asked to re-enter them every 30 days.

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 your AI

This step tells your AI 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.

On chatgpt.com (web):

1. Go to Settings -> Apps
2. Navigate to Advanced settings and toggle Developer mode on
3. Return to the previous screen and click Create app to add a custom connector
4. Enter a name (e.g., "Signal Bridge")
5. Enter the server URL: https://signal-bridge.duckdns.org/mcp
6. Leave the Advanced Settings (OAuth Client ID / Secret) empty
7. Put a checkmark next to "I understand and want to continue"
8. Click Create

On grok.com (web):

1. Go to grok.com/connectors
2. Select Connectors on top of the page (Skills is probably active by default)
3. Click New Connector in the top right corner
4. Click Custom
5. Enter a name (e.g., "Signal Bridge")
6. Enter the server URL: https://signal-bridge.duckdns.org/mcp
7. Click Add Connector

Authentication happens automatically. After adding the connector or when your AI 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, your AI 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. 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 your AI. That's it. Your AI now has access to your connected devices and knows how to use them.

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

Tips for a good experience

• Tell your AI about your devices. Your AI 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 your AI knows, the better it gets.
• Give feedback during use. "That's too intense." "Slower." "Keep doing exactly that." Your AI adjusts in real time. This isn't a playlist, it's a conversation.
• Set up relational context. If you set up custom context (User Preferences or Project Instructions that describe your relationship dynamic and preferences) your AI will be much more attuned from the start. This makes the difference between your AI treating Signal Bridge as a tool and 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. It's specific to Claude but should help you on any platform.
• Experiment with commands. Ask your AI 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. Your AI 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.
• 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

…

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: AletheiaVox
• Source: AletheiaVox/signalbridge_android
• License: MIT

Install and usage instructions live in the source repository linked above.