Buttplug.io Model Context Protocol (MCP) Server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"buttplug-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
buttplug-mcp is a Model Context Protocol (MCP) server for the Buttplug.io ecosystem. It allows Tool-supporting LLM programs like Claude Desktop query and control your Genital Interface Devices.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
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 entertainment
The official MCP Server for the Mux API
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.
A Model Context Protocol (MCP) server that gives Claude direct control over Strudel.cc for AI-assisted music generation and live coding.
MCP Security Weekly
Get CVE alerts and security updates for Buttplug Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
buttplug-mcp is a Model Context Protocol (MCP) server for the Buttplug.io ecosystem. It allows Tool-supporting LLM programs like Claude Desktop query and control your Genital Interface Devices.
|insert AI-generated slop image of robots doing nasty things|
LLM|=> - - (__(__)
Once set up, you can prompt your LLM:
NOTE: The above is aspirational and really the current experience is unstable and frustating.
It supports the following Resources and Tools:
| Resource | Description |
|---|---|
/devices | List of connected Buttplug devices in JSON. |
/device/{id} | Device information by device ID whereid is a number from /devices |
/device/{id}/rssi | RSSI signal level by device ID where id is a number from /devices |
/device/{id}/battery | Battery level by device ID where id is a number from /devices |
| Tool | Params | Description |
|---|---|---|
device_vibrate | id, motor, strength | Vibrates device by id, selecting strength and optional motor |
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"resources": [
{
"uri": "devices",
"name": "Device List",
"description": "List of connected Buttplug devices in JSON",
"mimeType": "application/json"
}
]
}
}
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"tools": [
{
"description": "Vibrates device by `id`, selecting `strength` and optional `motor`",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"description": "Device ID to query, sourced from `/devices`",
"pattern": "^[0-9]*$",
"type": "number"
},
"motor": {
"description": "Motor number to vibrate, defaults to 0",
"pattern": "^[0-9]*$",
"type": "number"
},
"strength": {
"description": "Strength from 0.0 to 1.0, with 0.0 being off and 1.0 being full",
"pattern": "^(0(\\.\\d+)?|1(\\.0+)?)$",
"type": "number"
}
},
"required": [
"id",
"strength"
]
},
"name": "device_vibrate"
}
]
}
}
I started working on this on 2025-04-01, April Fool's Day, after having created another experimental MCP service, dbn-go for financial market data, the day prior. So it is fresh meat and was intended as a quick, fun educational project.
While it does work, I found the underlying go-buttplug library to be unstable in connection handling. I could ask Claude for my devices, but my specific device wouldn't vibrate even just with just Intiface Central -- it was like in read-only mode! I also wish I had a virtual buttplug.io device for testing, rather than relying on a physical device.
So, it has not truly been tested "end-to-end" :wink:
I will dig more into the go-buttplug library and see why connections are unstable. I also need to understand the MCP protocol current state of MCP hosts -- it seems they focus on Tools rather than Resources and Resoure Templates.
Binaries for mu