buttplug-mcp - Buttplug.io MCP Server

Name: buttplug-mcp - Buttplug.io MCP Server
Author: ConAcademy

@ConAcademy

Repository

About buttplug-mcp - Buttplug.io MCP Server

Buttplug.io Model Context Protocol (MCP) Server

#mcp #buttplug #llm #mcp-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "buttplug": {
      "command": "/opt/homebrew/bin/buttplug-mcp",
      "args": [
        "--ws-port",
        "12345"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is buttplug-mcp?

buttplug-mcp is a Model Context Protocol (MCP) server for the Buttplug.io ecosystem. It allows Tool-supporting LLM programs like Claude Desktop to query and control Genital Interface Devices. It was created on April Fool's Day 2025 as a quick, fun educational project and is currently unstable and frustrating.

How to use buttplug-mcp?

Download Intiface Central to manage your devices, start it, and note the server port (default 12345). Configure your MCP host (e.g., Claude Desktop) with the command and --ws-port argument. You can also use it with Ollama and the mcphost tool. Install via Homebrew (brew install conacademy/tap/buttplug-mcp) or download a binary from GitHub Releases.

Key features of buttplug-mcp

Exposes device listing, battery, and RSSI as resources
Provides a device_vibrate tool with motor and strength control
Supports STDIO and SSE transport modes
Configurable logging to file or JSON format
Works with multiple MCP-compatible hosts and local LLMs

Use cases of buttplug-mcp

Query connected buttplug devices from an LLM
Set motor strength on a specific device by ID
Check battery level of a connected device
Read RSSI signal level of a device

FAQ from buttplug-mcp

Does buttplug-mcp work reliably?

No. The current experience is unstable and frustrating. The underlying go-buttplug library has unstable connection handling, and the developer could not get their physical device to vibrate even with Intiface Central. It has not been truly tested end-to-end.

What are the runtime requirements?

You need Intiface Central running (default port 12345) and a physical or emulated buttplug device. The server connects via Websocket to the Buttplug server. Binaries are available for multiple platforms via GitHub Releases or Homebrew.

What data does buttplug-mcp access?

It reads device information, battery levels, and RSSI signal levels from connected devices via Intiface Central's Websocket server. Data is returned as JSON via MCP resource URIs like /devices, /device/{id}, /device/{id}/battery, and /device/{id}/rssi.

Which transports and hosts are supported?

Both STDIO and SSE transport are supported. It has been tested with Claude Desktop and mcphost (for Ollama), though only Tools appear to work in mcphost — Resources may not be supported by some MCP hosts.

Is authentication or encryption supported?

The README does not mention any authentication or encryption mechanisms. The server connects to a local Intiface Central instance on a configurable port (default 12345) over plain Websocket.