Repository avatar
Other Tools
v1.2.0
active

ache

io.github.NTRanch/ache

ache: unified haptics MCP: Lovense + Buttplug.io behind one surface, gated by decide()

Documentation

ache — unified haptics

ache — unified haptics, by Nice Thoughts Ranch

crates.io

Home of ache, Nice Thoughts Ranch's unified haptics MCP server, and of the Lovense integration work around it: the studio's presence in the Lovense App Gallery, toy integration for STROBE, and media-sync research for future interactive media.

This is a planning and integration repo. It contains no credentials. Its production code is the MCP server in mcp/ — ache, the unified haptics server (Lovense Standard API local route + embedded Buttplug + the opt-in Server API cloud route, behind one gated tool surface), built under the checklist gates below.

Start here

  • mcp/README.md: ache, the unified haptics MCP server — its safety contract, tool surface, and configuration.
  • CHECKLIST.md: the phased work list, account and console setup first, code last.
  • TESTING.md: the test ladder for the integration, mock first, live hardware last and gated.
  • DOCS-NOTES.md: condensed notes from the official Lovense developer documentation (read 2026-10-20), including the per-plugin capability matrix and the sub-pages still to read.
  • TOYS.md: the current Lovense developer-program toy catalog (24 devices with product pages).
  • EXAMPLES.md: three Lovense games read as design references (Projekt Melody, Iced Coffee with Breastmilk, CumPartment), with what STROBE takes from each.

Roadmap

  • Now — v1.0.0 (live on crates.io). The unified gated server: Lovense Standard API (local Game Mode route) + embedded Buttplug behind one tool surface, every output through the pure decide() gate. 10 tools.
  • In release prep — v1.1.0. Symphony, the multi-toy score layer: per-device parts planned through the same gate, concurrent dispatch, one ensemble latching stop. Plus the MCP Registry listing under io.github.NTRanch/ache.
  • In development. An optional Server API provider for true internet remote play — off by default, behind the same gate, developer token held in the user's password store, QR pairing as an explicit user act. Local custody stays the default.
  • In production. A live interactive demo: an animated performer whose reactions are driven in real time through ache, with genuine live device switching between toys on screen.
  • Design stage. Muse Gadgets: a physical stop button and an e-ink status surface for the gate's state (armed, ceiling, watchdog) — hardware witnesses to the contract, not decorations.
  • Hardware ladder. Live-device verification rungs, mock first, hardware last and gated, per TESTING.md.

Toy coverage

ache covers the full Lovense catalog below. One honesty rule governs the whole table: Lovense publishes no static per-toy function list — a connected toy reports its functions at runtime (GetToys), and ache reads the reported capabilities and drives only what is reported. The functions below are the expected reported set per toy. Features with no API action (heating, tapping, touch-sense) are named as app-only or input-only — the gate refuses them by name rather than pretending to map them.

Routes: GM = Lovense Game Mode / Standard API via the Remote app (local LAN); BLE = direct Bluetooth via the embedded Buttplug provider.

ToyHow ache controls itRoute
AmbiVibrateGM + BLE
CalorVibrate — heating is app-only (no API action; refused by name)GM + BLE
DiamoVibrate (multi-motor)GM + BLE
DolceVibrate ×2 motorsGM + BLE
Domi 2VibrateGM + BLE
Edge 2Vibrate ×2 motorsGM + BLE
ExomoonVibrate (generic BLE match)GM + BLE
FerriVibrateGM + BLE
FlexerVibrate ×2 + Fingering (modelled as a rotate feature on BLE)GM + BLE
GeminiVibrate ×2 motorsGM + BLE
GravityVibrate + Thrusting (modelled as oscillate on BLE)GM + BLE
GushVibrateGM + BLE
Hush 2VibrateGM + BLE
HyphyVibrate ×2 motorsGM + BLE
KrakenVibrate (generic BLE match)GM + BLE
LapisVibrate ×3 motors (tip / internal / external)GM + BLE
Lush 3VibrateGM + BLE
Max 2Vibrate + Pump + Suction (pump modelled as constrict on BLE)GM + BLE
NoraVibrate + RotateGM + BLE
Osci 2Vibrate + Oscillate on GM; BLE models vibration onlyGM + BLE
RidgeVibrate + RotateGM + BLE
Sex MachineOscillateGM + BLE
SolaceThrusting + Fingering on GM; oscillate only on BLEGM + BLE
VulseVibrate + Thrusting on GM; BLE models vibration onlyGM + BLE
Lush 4Vibrate — LED tail lighting is app-onlyGM + BLE
Lush 2VibrateGM + BLE
Lush MiniVibrate (generic BLE match)GM + BLE
GlintVibrate (generic BLE match) — touch-sense is input-only, never an outputGM + BLE
SpinelVibrate + Thrusting (modelled as oscillate on BLE) — heating is app-onlyGM + BLE
FizzSuction — tapping has no API action; refused by nameGM + BLE
Mission 2Vibrate — touch-sense is input-only, never an outputGM + BLE
VelvoVibrate + Rotate (the rolling bead is modelled as rotation)GM + BLE
Tenera 2Suction on GM; the generic BLE match does not model suctionGM + BLE
Osci 3Vibrate + Oscillate — warming is app-onlyGM + BLE
Mini Sex MachineOscillateGM + BLE
Ferri ReserveVibrateGM + BLE

Storefront models (below the developer-program 24 in the table) link to the Lovense store; per-toy control detail is in the coverage research behind TOYS.md. Solace Pro is covered by the same gate vocabulary (Position / Stroke / Depth) and is driven wherever it reports those functions.

The Lovense surfaces, and which ones are ours

Lovense publishes several unrelated API families. Keeping them straight is most of the work:

  1. Standard API (Game Mode, local LAN). The game talks directly to the Lovense Remote app on the player's network. This is STROBE's integration route; a gated bridge implementation already exists in the STROBE project (master toggle defaults off, output clamped in the bridge, stop is first-class). The server route of the Standard API (commands relayed through Lovense's cloud with a developer token) was evaluated and rejected for STROBE on latency and token-custody grounds. For ache itself the posture was later amended (D-1451): ache's Server API provider implements the server route behind the same gate, opt-in and off by default, with the token referenced by password-store path only — see mcp/README.md.
  2. App Gallery platform API. For apps hosted inside Lovense Remote's App Gallery. This is the surface behind the App Gallery Console (public profile, app listings). New territory for the studio; Phase 0 and Phase 4 of the checklist cover it.
  3. Pattern Editor / Media Sync SDK. A web JavaScript SDK (pattern-sdk.js) that syncs toys to web audio/video, with FunScript and Lovense pattern support and an AI sync fallback. Relevant only if the studio ships web media; tracked as research in Phase 5.
  4. Game engine plugins. Six Unity plugins (Universal Remote, Android, iOS, Windows Bluetooth, USB Dongle, Mac), an Unreal Remote plugin, a Windows BLE DLL for C/C++/C#, and a Ren'Py plugin. The Unity Windows and Dongle plugins are the evaluation candidates for STROBE's Windows build; see DOCS-NOTES.md for the capability matrix.
  5. Native SDKs. iOS, Android, and Windows SDKs for standalone apps. Not currently planned; noted for completeness.

Credentials

Developer credentials (token, key, IV) live in the studio password store under lovense/ntr/ and are referenced by path only. They are never committed to this repo, never pasted into issues or chat, and are used only by the server-side flows that require them.

Official documentation

License

Apache-2.0. See LICENSE.