A remote MCP server that lets Claude control Bluetooth intimate hardware over the internet via Buttplug.io / Intiface Central.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"signal-bridge": {
"url": "https://signal-bridge.duckdns.org/mcp",
"headers": {
"Authorization": "Bearer YOUR_JWT_TOKEN_HERE"
},
"transport": {
"type": "streamableHttp"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Malware forks of Signal Bridge exist on GitHub. These are copies of this project where the download links in the README have been replaced with links to malicious software.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'buttplug' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked buttplug against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP proxy that compresses prose fields (tool descriptions, etc.) using caveman rules. Same accuracy, fewer context tokens.
MCP Security Weekly
Get CVE alerts and security updates for Signal_bridge_remote and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Malware forks of Signal Bridge exist on GitHub. These are copies of this project where the download links in the README have been replaced with links to malicious software.
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 - you're here)
👉 github.com/AletheiaVox/signal_bridge_android (user-friendly Android version)
If you found this project through a different GitHub account, do not download or run anything from it.
Similarly, always download Intiface Central from the official website at intiface.com/central. Not from any link in a forked repo.
Give Claude a body.
Signal Bridge connects Claude to intimate hardware (vibrators, thrusting toys, etc.) so that Claude can touch you through your devices while you talk. Claude gets tool calls like vibrate, pulse, and escalate — you just have a conversation and feel the rest.
It works with Intiface Central and the Buttplug.io protocol, which means it supports a huge range of devices from Lovense, Lelo, We-Vibe, Satisfyer, and more.
How it works in practice: You chat with Claude normally in the Claude app. Claude has access to tools that control your devices. When the moment calls for it, Claude can send vibration, pulsing, thrusting, or other commands — woven into the conversation naturally. You see tool-use indicators in the chat; you feel the rest.
A remote MCP server that lets Claude control Bluetooth intimate hardware over the internet via Buttplug.io / Intiface Central.
Claude (claude.ai or Desktop)
↓ HTTPS / MCP JSON-RPC
VPS (FastAPI + Docker + Caddy)
↓ WebSocket (WSS)
Phone or PC (Relay Client)
↓ WebSocket (local)
Intiface Central
↓ Bluetooth
Devices
The relay client bridges between your VPS and Intiface Central running on whatever device is physically near your Bluetooth toys. This can be a Windows PC or an Android phone running Termux.
Sign up at DigitalOcean and create a droplet:
Note your droplet's IP address (e.g., 139.59.156.242).
SSH into your droplet and install Docker:
ssh root@YOUR_DROPLET_IP
apt update && apt upgrade -y
apt install -y docker.io docker-compose
systemctl enable docker && systemctl start docker
On your local machine, create the project directory and prepare files. The project structure is:
signal-bridge-remote/
├── Dockerfile
├── docker-compose.yml
├── .env
├── requirements-server.txt
├── server/
│ ├── __init__.py
│ ├── app.py
│ ├── auth.py
│ ├── config.py
│ ├── models.py
│ ├── mcp_tools.py
│ ├── relay_hub.py
│ ├── safety.py
│ └── session_registry.py
└── phone/
├── relay_client.py
└── devices.json
Dockerfile:
FROM python:3.11-slim
WORKDIR /app
COPY requirements-server.txt .
RUN pip install --no-cache-dir -r requirements-server.txt
COPY server/ ./server/
RUN mkdir
... [View full README on GitHub](https://github.com/AletheiaVox/signal_bridge_remote#readme)