Buttplug MCP Server

Overview

buttplug‑mcp bridges the gap between AI assistants that support the Model Context Protocol (MCP) and the Buttplug.io ecosystem, which is widely used for controlling a range of sex‑tech devices such as vibrators, dildos, and other pleasure gadgets. By exposing a set of RESTful resources and tools over MCP, the server allows an LLM‑powered assistant—like Claude Desktop—to query device status and issue control commands without needing custom integration code. This solves a common developer pain point: the lack of a unified, machine‑readable interface for interacting with diverse hardware that traditionally requires vendor‑specific SDKs or Bluetooth APIs.

The server provides a lightweight, opinionated API that maps directly to the capabilities of Buttplug.io devices. It offers resources for enumerating connected devices (), retrieving detailed device information (), and checking operational metrics such as signal strength () and battery level (). In addition, it supplies a single, well‑documented tool——which accepts a device ID, an optional motor index, and a strength value between 0.0 and 1.0. This tool enables natural‑language commands like “Set the second motor on my LELO F1S to 50 % strength” or “Turn off the vibrator in my Lovense Max.” By exposing these actions through MCP, developers can write AI prompts that translate directly into concrete device operations, making the experience feel seamless and conversational.

Key capabilities include:

• Unified discovery: The resource lists all connected devices in a single JSON payload, eliminating the need for multiple discovery protocols.
• Fine‑grained control: The tool supports per‑motor strength settings, allowing precise choreography or multi‑device synchronization.
• Real‑time status: RSSI and battery endpoints provide live feedback, which can be used to trigger safety checks or adaptive behavior in the assistant.
• Extensibility: The MCP schema can be expanded to include additional tools (e.g., temperature control, motion sensors) as Buttplug.io’s feature set grows.

In practice, this server is ideal for developers building “intelligent pleasure” applications. For example, a wellness chatbot could monitor battery levels and prompt the user to recharge devices before a session. A creative storytelling assistant might orchestrate a multi‑device performance, adjusting vibration patterns in response to user emotions inferred from text. Because the server speaks MCP—a protocol already understood by Claude and other LLMs—developers can focus on higher‑level logic rather than low‑level Bluetooth or USB communication.

Unique advantages stem from the tight coupling between Buttplug.io’s robust device abstraction and MCP’s declarative tool model. Developers benefit from a single, well‑defined contract that can be queried or invoked by any MCP‑compatible assistant. This reduces integration friction, speeds up prototyping, and opens the door to a broader ecosystem of AI‑driven experiences that blend natural language with tactile feedback.