Massage Chair MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Exact Bluetooth name of the chair, set in ~/.udiva_config.json. | |
| address | No | Bluetooth address of the chair, set in ~/.udiva_config.json to pin the chair so a nearby device spoofing its name can't be picked up. | |
| max_massage_minutes | No | Time limit for a massage in minutes (configurable, 10 to 240 minutes; default 120), set in ~/.udiva_config.json. | 120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Controls an OSIM uDiva3 massage chair over Bluetooth.
CHOOSING A MASSAGE — prefer a built-in factory program:
When the user wants a massage, FIRST try to match their intent to a built-in factory program. Call list_presets to see them and start_preset to run one. Factory programs are the most reliable: the chair runs them autonomously (full positioning + technique sequencing) and confirms they engaged. Rough matching: sleep/wind-down -> sweet_dreams or nap; intense/deep -> deep_tissue or sports_recovery; neck & shoulders -> shoulders_care or shoulder_blades; lower back -> lumbar_delight; light/relaxing -> gentle, spa, or beauty; general/full-body -> signature or spa.
Use a CUSTOM routine (list_custom_presets / run_custom_preset) or MANUAL control (enter_manual_mode + technique tools) only when no factory program fits, or the user explicitly asks for custom/manual control or a specific combination of techniques/zones. Manual is less reliable and slower to set up.
SESSION FLOW: you do NOT need to call connect_chair or power_on manually — every action tool auto-connects and auto-powers-on as needed. Simply ask for a massage and everything is handled. To switch programs mid-session just call stop then start the next one — do NOT return to sofa between programs. Only use return_to_sofa when the user is finished / leaving the chair (then optionally disconnect_chair). disconnect_chair and server shutdown leave the chair resting on their own. The OSIM phone app must be disconnected first — the chair allows only one Bluetooth connection at a time.
TIME LIMIT: for safety the server stops any massage automatically once it has run for a set time (get_status shows the minutes so far and the limit; default 120). If that happens and the user wants more, just start a new one.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_chairA | Connect to the chair over Bluetooth and run the required handshake. Usually not needed — all action tools auto-connect. Call this explicitly only if you want to pre-warm the connection. The OSIM phone app must be disconnected (the chair allows only one Bluetooth connection). |
| power_onA | Move the chair into its active run-state so it's ready to start a program. (The chair is already powered at the wall — this is the 'begin' toggle, not a true power switch.) Auto-connects if not already connected. Usually not needed explicitly: start_preset and enter_manual_mode do this themselves. |
| power_offA | Stop all massage (including a running custom routine) and take the chair out of its run-state. |
| stopA | Stop the current massage — a factory program, manual massage, or custom routine — and return the chair to idle (it stays powered, ready for another program). |
| return_to_sofaA | Return the chair to its default sofa/resting position (backrest up, footrest down). Stops any running massage/routine first. Takes up to ~35s while the seat moves. |
| disconnect_chairA | Disconnect from the chair over Bluetooth, freeing it for the OSIM phone app or another client. Stops any running routine first. Call connect_chair again to reconnect. |
| get_statusA | Report the chair's state: connected, powered, running, program id, which manual techniques are active, and the custom routine (running, or how the last one ended). |
| list_presetsA | List the built-in factory massage programs with a short hint for each. PREFER these over manual/custom control when one matches the user's intent — they are the most reliable (the chair positions and sequences them itself). |
| start_presetA | Start a named built-in massage program. Powers on first if needed and confirms the program engaged. Stops any running custom routine. Args: name: e.g. 'spa', 'deep_tissue', 'sweet_dreams', 'shoulders_care', 'lumbar_delight', 'sports_recovery', 'nap', 'detox', 'gentle'. Use list_presets for the full set. |
| enter_manual_modeA | Start a manual massage and position the chair, ready for technique steps. PREFER a factory program (list_presets / start_preset) when one fits the user's intent — use manual only for specific technique/zone combinations or when the user explicitly wants manual control. This drives the chair to the massage position and deploys the rollers (auto shoulder-detect), then settles. It does NOT start any technique by itself — after this, turn on a technique (set_kneading/set_tapping) to actually start the rollers, then adjust rolling / zone intensity / shoulder position. Args: area: 'back' for a Back Body roller massage (default), or 'head_neck' for a Head & Neck (V-grip) massage. Powers on first if needed. Stops any running custom routine. Takes up to ~60s while the chair positions. |
| set_tappingA | Turn back TAPPING on/off (combinable with kneading and rolling). Requires manual mode. |
| set_kneadingA | Turn back KNEADING on/off (combinable with tapping and rolling). Requires manual mode. |
| set_rollingA | Set back ROLLING. level: 'off', 'partial', or 'full'. Combinable with tapping and kneading. Requires manual mode. |
| set_shoulder_positionA | Set the shoulder roller height, 1 (lowest) to 5 (highest). Requires manual mode. |
| set_zone_intensityA | Set 3D roller intensity for a back zone (requires manual mode with a technique active). Args: zone: 'shoulder', 'back', or 'lumbar'. level: 0 (off) to 5 (max). Intensity scales whichever technique is active at that zone; the shoulder zone is the most reliably responsive. |
| set_vgripA | Turn the head/neck V-grip on/off. Requires manual mode. Rollers take a few seconds to reach the neck. |
| set_leg_kneadingC | Set leg/calf kneading: 'off', 'low', or 'high'. |
| set_leg_vibrationC | Set leg/foot vibration: 'off', 'low', or 'high'. |
| quick_startA | One-shot: connect (if needed), power on, and start a preset program. Args: preset: a preset name (default 'spa'), or 'manual' for a manual back massage. |
| list_custom_presetsA | List user-defined and built-in custom massage routines (distinct from the chair's factory presets). |
| get_custom_presetB | Show the step-by-step definition of a custom routine as JSON. |
| save_custom_presetA | Save a custom massage routine. Args: name: a short name (e.g. 'my_evening'). steps_json: a JSON array of step objects. Supported actions: {"action":"manual","area":"back"} (or "head_neck"; positions the chair + deploys the rollers) {"action":"seat_sofa"} / {"action":"seat_upright"} / {"action":"seat_recline"} (seat posture only) {"action":"tapping","on":true|false} {"action":"kneading","on":true|false} {"action":"rolling","level":"off|partial|full"} {"action":"intensity","zone":"shoulder|back|lumbar","level":0-5} {"action":"position","value":1-5} (shoulder roller height) {"action":"vgrip","on":true|false} {"action":"leg_kneading","level":"off|low|high"} {"action":"leg_vibration","level":"off|low|high"} {"action":"wait","seconds":N} {"action":"preset","name":"spa"} {"action":"stop"} description: optional human description. Pattern that works: start with {"action":"manual","area":"back"} (it positions the chair and deploys the rollers), then turn on an ENGAGING technique FIRST — {"action":"kneading","on":true} (or tapping) — which is what actually starts the rollers. Only after that do rolling / intensity / position adjustments take effect. |
| delete_custom_presetB | Delete a user-saved custom routine (built-ins cannot be deleted). |
| run_custom_presetA | Start a custom routine. It runs in the background so you can check status or stop it at any time. Connects/powers on first if needed. |
| stop_custom_presetA | Stop a running custom routine and bring the chair to idle. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
There are three overlapping start paths (start_preset, quick_start, run_custom_preset) and three overlapping stop paths (stop, power_off, stop_custom_preset), and stop already claims to stop custom routines, making stop_custom_preset largely redundant. The fine-grained set_* technique tools are clearly distinct, and the descriptions do explain the power_on/power_off vs stop nuance, but an agent still has to reason carefully to pick the right start/stop tool.
Mostly a consistent verb_noun snake_case scheme: get_status, list_presets, start_preset, set_kneading, save_custom_preset, delete_custom_preset, connect_chair. Minor deviations are the bare 'stop' and the vaguer 'quick_start'/'power_on' pair, but overall the pattern is predictable.
25 tools is heavy for a single massage chair. The eight set_* technique setters are justified by the hardware, but the connection lifecycle (connect_chair/disconnect_chair, described as usually unnecessary) and the six custom-preset management tools push it past a comfortable scope.
Lifecycle coverage is strong: power/connect, status, factory presets, manual positioning plus all techniques, custom preset CRUD and execution. The notable gap is seat posture adjustment (seat_sofa/seat_upright/seat_recline) which is only reachable as a step inside a saved custom routine, not as a direct tool.