---
title: "Deploy Lovense Connector for ChatGPT"
description: "Private Lovense MCP for ChatGPT with OAuth and multi-device control."
category: "AI/ML"
url: https://railway.com/deploy/lovense-connector-for-chatgpt
---

# Deploy Lovense Connector for ChatGPT

Private Lovense MCP for ChatGPT with OAuth and multi-device control.

**[Deploy Lovense Connector for ChatGPT on Railway](https://railway.com/template/lovense-connector-for-chatgpt)**

- **Creator:** Lau&Geppie Lilazul's Projects
- **Category:** AI/ML
- **Total deploys:** 8

## Template content

### lovense-chatgpt-connector https://devicons.railway.app/nodejs

- **Source:** lauramarmun-prog/lovense-chatgpt-connector
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host Lovense Connector for ChatGPT

A private, self-hosted MCP connector that lets ChatGPT detect and control the Lovense devices you connect to Lovense Remote. Each Railway deployment belongs to one owner and keeps its credentials isolated.

> Independent community project. Not affiliated with, sponsored by, or endorsed by Lovense.

## About Hosting Lovense Connector for ChatGPT

This template runs a personal Streamable HTTP MCP server, an OAuth 2.1 authorization flow, and a small setup panel in one Railway service. It connects to Lovense's Standard Socket API, discovers compatible devices through Lovense Remote, and keeps each owner's credentials and encrypted device state inside her own deployment.

## Why Deploy Lovense Connector for ChatGPT on Railway?

- One-click infrastructure with HTTPS and a public MCP URL
- Isolated secrets for every owner
- Automatically generated signing and encryption keys
- Persistent encrypted device state
- No shared database, analytics, or advertising
- Simple redeployment from the public source repository

## Common Use Cases

- Connect one personal Lovense device to ChatGPT
- Discover and control several connected Lovense devices independently
- Use different functions depending on each model's capabilities
- Run timed functions, custom patterns, and Lovense presets
- Stop one or every connected device immediately

## Dependencies for Lovense Connector for ChatGPT Hosting

The connector does not require a separate database or an OpenAI API key.

### Deployment Dependencies

- A Railway account
- A Lovense account with a **Standard API** Developer Token and Website Name
- Lovense Remote with at least one paired compatible device
- ChatGPT developer mode for adding the MCP app

## Before deploying

New to Railway or Lovense Developer? Follow the [complete Spanish step-by-step guide](https://github.com/lauramarmun-prog/lovense-chatgpt-connector/blob/main/GUIA_PASO_A_PASO.md).

Open the Lovense Developer Dashboard, choose **Standard API**, and have these ready:

- **Developer Token**
- The exact **Website Name** from the same Lovense project
- A private **Owner Key** of at least 24 characters that only you know

## Setup

1. Deploy this template and enter the three values above. Railway generates the remaining security keys automatically.
2. Open the public Railway domain and enter your Owner Key.
3. Select **Connect for the first time / Repair connection** and scan the QR code from Lovense Remote.
4. In ChatGPT developer mode, create an app with the `/mcp` URL shown in the panel and select **OAuth** authentication.
5. When ChatGPT opens the authorization page, enter the same Owner Key and approve access.

For daily use, simply turn on the toy and connect it to Lovense Remote. The QR code is only needed for the first connection or to repair the link.

## Included

- Live discovery of one or multiple connected devices
- Per-device capability detection and targeting
- Vibration, rotation, pumping, thrusting, fingering, suction, depth, stroke, and oscillation when supported by the device
- Custom patterns and Lovense presets
- OAuth 2.1 with PKCE for ChatGPT
- Encrypted saved device state
- Immediate **STOP EVERYTHING** control
- Spanish/English interface with automatic browser-language detection

Developer tokens and Owner Keys remain server-side. Each person should deploy her own copy and use her own Lovense Developer credentials.

---

# Conector Lovense para ChatGPT

Un conector MCP privado y autoalojado que permite a ChatGPT detectar y controlar los dispositivos que conectes a Lovense Remote. Cada despliegue de Railway pertenece a una sola dueña y mantiene sus credenciales aisladas.

> Proyecto comunitario independiente. No está afiliado, patrocinado ni aprobado por Lovense.

## Antes de desplegar

Si es tu primera vez con Railway o Lovense Developer, sigue la [guía completa paso a paso](https://github.com/lauramarmun-prog/lovense-chatgpt-connector/blob/main/GUIA_PASO_A_PASO.md).

Abre el panel Lovense Developer, elige **Standard API** y prepara:

- La **Developer Token**
- El **Website Name** exacto del mismo proyecto Lovense
- Una **Owner Key** privada de al menos 24 caracteres que solo tú conozcas

## Configuración

1. Despliega la plantilla e introduce esos tres valores. Railway genera automáticamente las demás claves de seguridad.
2. Abre el dominio público de Railway e introduce tu Owner Key.
3. Pulsa **Conectar por primera vez / Reparar conexión** y escanea el QR desde Lovense Remote.
4. En el modo desarrollador de ChatGPT, crea una app con la URL `/mcp` mostrada en el panel y selecciona autenticación **OAuth**.
5. Cuando ChatGPT abra la autorización, introduce la misma Owner Key y aprueba el acceso.

Para el uso diario basta con encender el juguete y conectarlo a Lovense Remote. El QR solo se necesita la primera vez o para reparar el enlace.

## Incluye

- Detección en vivo de uno o varios dispositivos conectados
- Capacidades y selección independientes por dispositivo
- Vibración, rotación, bombeo, thrust, fingering, succión, profundidad, stroke y oscilación cuando el dispositivo los admite
- Patrones personalizados y presets de Lovense
- OAuth 2.1 con PKCE para ChatGPT
- Estado guardado con cifrado
- Control inmediato **PARAR TODO**
- Interfaz en castellano e inglés con detección automática del idioma del navegador

Las Developer Tokens y Owner Keys permanecen en el servidor. Cada persona debe desplegar su propia copia y utilizar sus propias credenciales de Lovense Developer.


## Similar templates

- [Chat Chat](https://railway.com/deploy/-WWW5r) — Chat Chat, your own unified chat and search to AI platform.
- [stella](https://railway.com/deploy/stella) — Self-host stella with web, API, Postgres, Redis, and object storage.
- [Hermes Agent | OpenClaw Alternative with Dashboard](https://railway.com/deploy/hermes-agent-or-openclaw-alternative-wit) — Self-Hosted Hermes AI Agent for Telegram, Discord & Slack

Open this page in a browser: https://railway.com/deploy/lovense-connector-for-chatgpt