MCP Tools DirectoryAbout this integration
Content-agnostic control layer for intimate hardware; forwards Buttplug/Intiface commands only.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.2
- Package
- tactus-mcp
- Last compatibility test
- Not independently tested
Connect your agent
tactus-mcpLocal hardware control for consenting adults only, as stated by the publisher. Publisher README and package manifest reviewed from hash-pinned captures; the package, Intiface endpoint, and hardware were not executed or independently safety-audited.
Capabilities: Discover and inspect locally connected haptic devices, Control supported vibration, oscillation, rotation, and linear actuators, Apply watchdog, intensity-clamp, and emergency-stop controls
Connected profiles
Additional details
io.github.ProjectAILiberation/tactus
Source ↗ · Checked 2026-09-170.1.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17tactus-mcp
Source ↗ · Checked 2026-09-190.1.2
Source ↗ · Checked 2026-09-19Publisher documentation says Tactus runs locally over stdio via npx, maintains an independent watchdog, stops devices on disconnect or process signals, and retries the local Intiface connection with backoff.
Source ↗ · Checked 2026-09-19The complete publisher prerequisites and MCP configuration specify a local Intiface server, locally paired hardware, and safety settings, with no credential or user-authorization step documented. This is a documentation-based classification, not an executed authentication test.
Source ↗ · Checked 2026-09-19The MCP client launches npx -y tactus-mcp over stdio; Tactus connects to a locally running Intiface Central/Engine WebSocket at ws://127.0.0.1:12345 by default.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19