Lovense Cloud MCP Server

How to use

Connect Claude to the Lovense MCP server to start issuing commands. You can speak or type natural instructions like breaking down actions into presets or duration-based vibrations. The MCP translates your requests into toy actions, so you don’t need to interact with any separate apps beyond enabling the integration and pairing your Lovense toy with Claude.

How to install

Prerequisites before you begin:

• Node.js 18+ must be installed on your machine
• A Cloudflare account (free)
• A Lovense Developer Token

Step 1: Get your Lovense Developer Token. Sign in at Lovense developer portal, create your account, and copy your Developer Token from the dashboard.

Step 2: Install Wrangler (Cloudflare CLI). Open your terminal and run:

npm install -g wrangler

Then log into Cloudflare:

wrangler login

Step 3: Deploy the Worker. Unzip the folder you’ve downloaded and navigate to that folder in your terminal. Install dependencies and deploy the Worker:

npm install
```
```
npx wrangler deploy

You’ll be given a URL like https://lovense-cloud.YOUR-SUBDOMAIN.workers.dev. Save this URL for the next steps.

Step 4: Add your Lovense token to the environment used by the Worker. Replace YOUR_TOKEN_HERE with your actual token:

echo "YOUR_TOKEN_HERE" | npx wrangler secret put LOVENSE_TOKEN

Step 5: Add the server configuration to Claude. This config wires Claude to run the local bridge script and point to your deployed worker.

For Claude Desktop + Phone:
Windows: %APPDATA%\Claude\claude_desktop_config.json
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
```

Then insert the following into the "mcpServers" section, replacing paths and subdomain as needed:
```json
"lovense-cloud": {
  "command": "node",
  "args": ["C:\\path\\to\\lovense-cloud-worker\\bridge.js"],
  "env": {
    "LOVENSE_WORKER_URL": "https://lovense-cloud.YOUR-SUBDOMAIN.workers.dev"
  }
}
```
- Replace `C:\path\to\` with the folder path where you unzipped the project.
- Replace `YOUR-SUBDOMAIN` with your actual Cloudflare subdomain.
Restart Claude Desktop. Your phone Claude will sync automatically.

Step 6: Pair your Lovense toy to Claude. In Claude, say or type the pairing command, then scan the Lovense QR code in the Lovense Remote app to link your toy.

Step 7: Add the MCP entry in Claude Code (Code-only Claude). Use this command to add the server as an MCP transport over HTTP:

claude mcp add lovense-cloud --transport http "https://lovense-cloud.YOUR-SUBDOMAIN.workers.dev/mcp"

Additional configuration and usage notes

Two MCP connection methods are supported. Use the HTTP URL for a remote MCP connection, and a local stdio bridge for direct control via a node bridge script.

Environment variables shown here are required for the integration to work correctly. Keep your Lovense Developer Token secure and only expose the token in trusted environments.

Once connected, you can issue natural language commands like these to Claude to control your Lovense toy:

- vibrate at intensity 15 for 10 seconds - run the earthquake preset - edge me for 30 seconds - tease me - stop

Available presets include: pulse, wave, fireworks, earthquake. Intensity range is 0-20.

Troubleshooting

LOVENSE_TOKEN not configured — step 4 was not completed. Re-run the token setup to store your token securely.

QR code not working — ensure the Lovense Remote app is up to date. If needed, use the manual pairing code.

Claude can’t connect to MCP — verify the URL is correct and that the Claude Desktop app was restarted after changes.

Phone doesn’t have the MCP — add it to the Desktop app first, then restart Desktop so the phone can sync.

Notes and security

Only use explicit MCP URLs and commands shown in configuration snippets. Do not rely on external previews or badges to establish endpoints. Protect your Lovense Developer Token and limit access to trusted environments.

mcp bridge

Core bridge that connects Claude MCP to the Lovense API and relays toy control commands.

token provisioning

Securely store and inject your Lovense Developer Token into the MCP environment for authorized access.