buttplug

buttplug-mcp is an MCP server that exposes Buttplug.io device control over the MCP protocol. It lets LLM-enabled tools query connected genital-interface devices and issue simple commands such as listing devices, querying device details, reading RSSI and battery levels, and vibrating a device via the device_vibrate tool. The server is designed to work with clients like Claude Desktop or other MCP hosts that know how to discover and talk to MCP servers. You’ll typically run the server and point your MCP-enabled application to its WebSocket port (as configured, default 12345 in the example). The available resources include endpoints like /devices and /device/{id}, while the single tool exposed presently is device_vibrate, which vibrates a device by id with a specified strength (and an optional motor).

Prerequisites:

• A system with the required runtime (Go-based MCP server binary; instructions below show the distribution approach).
• Access to the internet to download binaries or install via Homebrew.

Installation steps (recommended):

1. Install the binary via GitHub Releases (cross-platform binaries are released):
   • Visit https://github.com/conacademy/buttplug-mcp/releases and download the appropriate binary for your OS.
   • Place the binary somewhere on your PATH, e.g. /usr/local/bin/buttplug-mcp.
2. Alternatively, install via Homebrew (macOS):
   • brew tap conacademy/homebrew-tap
   • brew install conacademy/tap/buttplug-mcp
3. Verify installation:
   • buttplug-mcp --version
4. Run the server with the configured WebSocket port (as shown in the example):
   • buttplug-mcp --ws-port 12345

If you want to build from source, you can follow the project’s Go-based build steps (noting that building locally may require Go tooling and the go-buttplug library):

• go build -o bin/buttplug-mcp cmd/buttplug-mcp/main.go

Notes and tips:

• The current MCP implementation emphasizes Tools over Resources; Resources (like enumerating devices) may be limited depending on the underlying library stability.
• If you experience unstable connections or non-responsive devices, ensure your physical device is properly connected to Intiface Central or your test harness, and be aware that the underlying go-buttplug library can have instability issues.
• The example configuration targets Claude Desktop; you can adapt the mcpServers configuration for other MCP hosts or local testing matches (e.g., mcphost with Ollama or other LLMs that support Tools).
• For testing tooling, you can use the provided testing commands such as the MCP Inspector or the npx tool inspector to validate schemas and tool descriptions.
• If you modify ports, ensure your MCP host configuration reflects the new port in the ws-port argument.