Content-agnostic control layer for intimate hardware; forwards Buttplug/Intiface commands only.
Most planning and project tracking work still happens through a UI a human drives. Tactus MCP server moves it into the conversation instead. Content-agnostic control layer for intimate hardware; forwards Buttplug/Intiface commands only.
Tactus is a thin, neutral control layer. It wraps Buttplug / Intiface — so a single integration reaches 750+ devices across ~26 brands — and exposes them to AI agents as Model Context Protocol (MCP) tools. It forwards hardware control commands only. It does not generate, host, or store any content of any kind.
The server publishes 11 tools. What each one is for:
list_devices — List connected devices and their actuatorsscan_for_devices — Scan for and return newly found devicesget_battery — Read battery level (0.0–1.0)vibrate — Set vibration intensity (0.0–1.0)oscillate — Set oscillation intensity (0.0–1.0)rotate — Set rotation speed and directionlinear — Move a stroker to a position over a durationvibrate_pattern — Play a timed, interruptible vibration patternstop_device — Stop one devicestop_all — Emergency stop — halt every device immediatelyserver_status — Report connection status to IntifaceConfiguration is passed through the environment: MAX_INTENSITY, INTIFACE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as tactus-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tactus's toolset — list_devices, scan_for_devices, get_battery and 8 more — is a fair guide to whether it matches your workflow. It is maintained by ProjectAILiberation; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_devices | List connected devices and their actuators |
| scan_for_devices | Scan for and return newly found devices |
| get_battery | Read battery level (0.0–1.0) |
| vibrate | Set vibration intensity (0.0–1.0) |
| oscillate | Set oscillation intensity (0.0–1.0) |
| rotate | Set rotation speed and direction |
| linear | Move a stroker to a position over a duration |
| vibrate_pattern | Play a timed, interruptible vibration pattern |
| stop_device | Stop one device |
| stop_all | Emergency stop — halt every device immediately |
| server_status | Report connection status to Intiface |
{
"mcpServers": {
"tactus": {
"command": "npx",
"args": ["-y", "tactus-mcp"],
"env": { "MAX_INTENSITY": "1.0" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MAX_INTENSITY | Configuration value read at startup. | Optional |
| INTIFACE_URL | Endpoint or connection string the server talks to. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.