lovense-mcp

English · 中文

By Rosalie

Overview

Control Lovense toys from the Claude app on your phone, in plain language. Deploy once; your computer can stay off.

This is an MCP server that runs on Cloudflare Workers and forwards commands through Lovense's official cloud interface (Standard API). Tested on a Lovense Vulse.

Three things it does differently:

• Phone-only after setup. The Worker is stateless and always on; the free tier is plenty.

• MCP spec 2026-07-28. Stateless Streamable HTTP, with fallback for older clients (2025-11-25 / 2025-06-18 / 2025-03-26), so both new and old Claude clients connect.

• Access key, fail-closed. The key lives in the URL path, no OAuth to configure. With no key configured, the Worker refuses every request.

Other Lovense toys use the same API and should work, but only the Vulse has been tested.

Adults only. Use only on devices you own.

Related MCP server: mcp-buttplug

How it works

A command leaves Claude, passes through the Worker and Lovense's cloud, and reaches the toy over Bluetooth from the Lovense Remote app on your phone.

Claude app (phone / web)
   │  MCP · Streamable HTTP · key in the URL
   ▼
Cloudflare Worker (this project)
   │  HTTPS · Lovense Standard API
   ▼
Lovense cloud
   │  pushed to the paired phone
   ▼
Lovense Remote app (phone)
   │  Bluetooth
   ▼
Toy

On each call the Worker does three things: checks the key in the URL, translates tool arguments into Lovense API calls, and forwards them. Pairing state lives on Lovense's servers; the Worker stores nothing.

Lovense commands carry their own duration, so one call runs for the requested time without the client re-sending. Few calls per session means the context cost is negligible.

Tools

Once the connector is attached, Claude sees 6 tools. You speak normally; Claude picks the tool.

Patterns run on the Vibrate channel by default; thrusting toys can pass function: "thrusting". Preset names and exact argument schemas are defined in src/tools.js.

Tested device: Lovense Vulse

The Vulse responds to lovense_vibrate only. lovense_thrust does nothing.

Lovense markets the Vulse as a thrusting egg (up to 120 strokes/min, 10 mm travel), so the thrust command looks like the obvious choice. In practice:

• Lovense Remote shows a single Vibration slider for it.

• The Lovense API exposes only the Vibrate channel. Thrust and vibration share one motor and cannot be driven separately.

• A Thrusting command returns success from the API, and the toy stays still.

So ask for "vibration" when driving a Vulse, and build patterns on the Vibrate channel too.

Thrusting toys such as the Solace should respond to lovense_thrust, but that is untested here. The Lovense API also has a Depth command (0–3); this project does not implement it.

Prerequisites

Everything is free. The computer is needed once, for deployment.

Deploy

If you have Claude Code, you can hand it the repo URL: "Deploy this repo to my Cloudflare and install whatever is missing." Apart from authorizing Cloudflare in the browser and pasting your token, it can run every command below.

1. Clone and install:

   git clone https://github.com/rosaliev24/lovense-mcp.git
   cd lovense-mcp
   npm install

2. Log in to Cloudflare (opens a browser to authorize):

   npx wrangler login

3. Generate an access key and keep it somewhere safe:

   node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"

4. Store your Lovense token and the access key. Paste at each prompt and press Enter; nothing shows while you paste, which is normal:

   npx wrangler secret put LOVENSE_TOKEN
   npx wrangler secret put MCP_ACCESS_KEY

   Do not pipe the value in with echo "xxx" | wrangler secret put; always paste interactively (see Troubleshooting).

5. Deploy:

   npx wrangler deploy

   The output shows your Worker address, like https://lovense-mcp.<subdomain>.workers.dev.

6. Verify (protocol checks only; sends nothing to the toy):

   node scripts/check.mjs https://lovense-mcp.<subdomain>.workers.dev <key>

7. Set the Lovense callback URL (required): at lovense.com/user/developer/info, set the Callback URL to

   https://lovense-mcp.<subdomain>.workers.dev/lovense/callback

   Without it, Lovense rejects the QR code request even with a correct token.

Connecting Claude

Add a custom connector

The connector URL is the Worker address + /mcp/ + your key:

https://lovense-mcp.<subdomain>.workers.dev/mcp/<key>

1. Open claude.ai in a browser → Settings → Connectors → Add custom connector.

2. Any name (e.g. Lovense), paste the URL above as the remote MCP server URL, leave both OAuth fields empty, click Add.

3. The connector's detail page should list 6 tools. Permissions default to "ask first"; switch to auto-allow once you trust it.

The iOS Claude app currently has no "add custom connector" entry. Add it on the web; the phone app picks it up after a restart.

Pair the toy (one time)

1. Open Lovense Remote on your phone and connect the toy over Bluetooth.

2. Start a new Claude conversation and ask for a pairing QR code. Approve the permission prompt on first use.

3. Scan the code from inside Lovense Remote. Codes expire within minutes; ask for a fresh one if it fails.

Pairing is stored on Lovense's servers. You will not need to scan again.

Daily use

Two steps each time: open Lovense Remote with the toy connected, then talk to Claude.

Examples:

• "Vibrate at 8 for 30 seconds"

• "Play one of the presets"

• "Ramp up from 3 to 15, five seconds per step"

• "Stop"

Claude picks the tool and fills in the arguments. Start low (around 3) for a few seconds the first time.

Keep in mind:

• Lovense Remote must stay running and the toy must stay connected over Bluetooth. If the app is killed, commands report success but nothing moves.

• Say "vibrate", not "thrust", for a Vulse (see Tested device).

• Each call costs roughly 100–200 tokens, plus a one-time ~1–2k for the tool definitions. An hour of play is a rounding error in context.

Security

The full connector URL is the credential. Anyone who has it can drive your toy. Do not screenshot it or paste it into chats.

• Fail-closed. With no MCP_ACCESS_KEY configured, the Worker returns 401 to everything; there is never an unprotected window. A wrong key also gets 401.

• Whitespace-tolerant key comparison, so a stray newline from copy-paste cannot lock you out.

• No secrets in code. The Lovense token and access key live in Cloudflare secrets, never in source or git. The locally generated .access-key.txt is in .gitignore.

• The Worker stores nothing. No command logs, no pairing data.

Rotating the key

If you suspect a leak, or the URL ever appeared in a chat log, rotate it:

node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"
npx wrangler secret put MCP_ACCESS_KEY    # paste the new key

Then update the URL in the claude.ai connector settings. The old URL stops working immediately; no redeploy and no re-pairing needed.

Troubleshooting

Every row below actually happened, listed in deployment order.

Known limitations

• Tested only on the Lovense Vulse. Other models are unverified.

• Depth is not implemented.

• Cloud only; Lovense's local LAN mode is not implemented.

• No OAuth. Auth is the key in the URL: fine for one person, not for sharing.

Development

npm test                    # unit tests, fully mocked, never touch a real device
npx wrangler dev            # local server, reads .dev.vars (see .dev.vars.example)
node scripts/check.mjs      # protocol checks against the local instance
npx wrangler tail           # live logs

Credits

• amarisaster/Lovense-Cloud-MCP: the original reference for the Cloudflare Worker approach.

• Lovense Standard API docs

• MCP specification 2026-07-28

• Code generated with Claude Code. Design, on-device testing and the troubleshooting above by Rosalie.

License

MIT © Rosalie. See LICENSE.