A new software project has emerged that connects artificial intelligence assistants like Claude to adult devices through the Model Context Protocol (MCP). The buttplug-mcp server allows users to control intimate hardware using natural language commands, representing an unusual application of AI technology in personal devices.
The project builds on the existing Buttplug.io ecosystem, which provides open-source standards for controlling various adult devices. By integrating with MCP, users can now ask AI assistants questions like What devices are connected? or Set the motor to 50% strength through conversational interfaces.
Supported Resources and Tools
| Resource | Description |
|---|---|
| /devices | List of connected Buttplug devices in JSON |
| /device/{id} | Device information by device ID |
| /device/{id}/rssi | RSSI signal level by device ID |
| /device/{id}/battery | Battery level by device ID |
| Tool | Parameters | Description |
|---|---|---|
| device_vibrate | id, motor, strength | Vibrates device by id, selecting strength and optional motor |
Technical Implementation and Challenges
The software works by connecting to the Intiface Central hub application, which manages device connections through Bluetooth protocols. Users can install the MCP server through package managers like Homebrew and configure it to work with AI assistants such as Claude Desktop or local models running on Ollama.
However, the developer notes significant stability issues with the underlying connection libraries. The project remains largely experimental, with the creator admitting that end-to-end testing has been problematic due to unreliable device connections and library limitations.
Installation and Configuration
Binary Installation:
- Available through GitHub releases for multiple platforms
- Homebrew installation:
brew tap conacademy/homebrew-tap && brew install conacademy/tap/buttplug-mcp
Configuration for Claude Desktop:
{
"mcpServers": {
"buttplug": {
"command": "/opt/homebrew/bin/buttplug-mcp",
"args": ["--ws-port", "12345"]
}
}
}
CLI Arguments:
--ws-port int: Port to connect to Buttplug Websocket server--sse: Use SSE Transport (default is STDIO)--log-file string: Log file destination--verbose: Enable verbose logging
Community Response and Industry Context
The tech community's reaction has been notably playful, with many developers making puns about common programming terms taking on new meanings in this context. Terms like penetration testing, injection attacks, and backdoor access have sparked humorous discussions about how industry jargon applies differently in this domain.
We were vibe coding before it was cool.
The project highlights an interesting aspect of the adult device market - many protocols have been reverse-engineered by enthusiasts rather than officially published by manufacturers. This grassroots approach to device control has created a surprisingly open ecosystem compared to other consumer electronics categories.
Security and Privacy Considerations
Several community members raised questions about security implications, particularly given the sensitive nature of the devices involved. The intersection of AI services, cloud connectivity, and intimate hardware creates unique privacy concerns that traditional IoT security frameworks may not adequately address.
The project represents part of a broader trend where developers are finding creative applications for AI integration beyond traditional business use cases. While the implementation remains experimental, it demonstrates how open protocols can enable unexpected connections between different technology domains.
The developer plans to continue working on stability issues and hopes to create virtual testing environments to improve development reliability. The project serves as both a technical experiment and a conversation starter about the expanding boundaries of AI-human interaction.
Reference: buttplug-mcp - Buttplug.io MCP Server