How do I use Dr. Dabber Switch 2 MCP?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Dr. Dabber Switch 2 MCP Discover nearby Switch 2 devices" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Dr. Dabber Switch 2 MCP

by nidamen

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Dr. Dabber Switch 2 MCP

A Model Context Protocol (MCP) server for controlling a Dr. Dabber Switch 2 vaporizer over Bluetooth LE. It exposes every safe user-facing control as a typed MCP tool, so any MCP-connected LLM or automation can discover, connect, and operate the device without touching the official app.

Problem it solves

The Switch 2 ships with a mobile/web Bluetooth app. This server bridges the device into the MCP ecosystem so you can drive it from Claude, Codex, or any other MCP client on your laptop or over a Raspberry Pi BLE proxy, keeping the device always reachable even when your phone app is not connected.

Related MCP server: discord-mcp

Install

Option A: run from GitHub (no clone needed)

npx -y github:nidamen/drdabber-switch2-mcp

Option B: local clone

git clone https://github.com/nidamen/drdabber-switch2-mcp.git
cd drdabber-switch2-mcp
npm install
npm run build

Node 20+ is required.

MCP client configuration

Direct BLE (laptop)

The server opens its own Bluetooth connection. The Switch 2 must be on, nearby, and not connected to another client.

Claude Desktop / claude_desktop_config.json:

{
  "mcpServers": {
    "drdabber-switch2": {
      "command": "npx",
      "args": ["-y", "github:nidamen/drdabber-switch2-mcp"],
      "env": {
        "DRDABBER_SWITCH2_TARGET": "My Switch 2"
      }
    }
  }
}

Or with a local build:

{
  "mcpServers": {
    "drdabber-switch2": {
      "command": "node",
      "args": ["/path/to/drdabber-switch2-mcp/dist/src/index.js"],
      "env": {
        "DRDABBER_SWITCH2_TARGET": "My Switch 2"
      }
    }
  }
}

Pi BLE proxy (always-on headless path)

When DRDABBER_PROXY_URL is set, the MCP forwards every command to the web control running on the Pi instead of opening its own BLE link. The Pi becomes the single BLE owner and multiple clients can share it without GATT contention.

{
  "mcpServers": {
    "drdabber-switch2": {
      "command": "node",
      "args": ["/path/to/drdabber-switch2-mcp/dist/src/index.js"],
      "env": {
        "DRDABBER_PROXY_URL": "http://192.168.1.44:4477"
      }
    }
  }
}

TOML style (Codex / Autohand):

[mcp_servers.drdabber-switch2]
command = "node"
args    = ["/path/to/drdabber-switch2-mcp/dist/src/index.js"]
env     = { DRDABBER_SWITCH2_TARGET = "My Switch 2" }

Environment variables

Variable	Required	Description
`DRDABBER_SWITCH2_TARGET`	No	BLE id or exact advertised name to prefer during scan. Omit to connect to the first Switch 2 found.
`DRDABBER_PROXY_URL`	No	Base URL of the Pi web control (e.g. `http://192.168.1.44:4477`). When set, all commands are proxied; BLE is not opened locally.

Transport

The server uses stdio MCP transport. It does not open any network ports itself. BLE communication runs via @abandonware/noble on the host machine, or via HTTP POST to the Pi proxy when DRDABBER_PROXY_URL is set.

Complete tool reference

Connection

Tool	Purpose	Parameters	Returns
`discover_switch2`	Scan for nearby Switch 2 devices advertising the `fee7` BLE service	`timeoutMs` (int, optional, 1000-60000)	Array of `{ id, name, rssi, services, connectable }`
`connect_switch2`	Connect to the Switch 2 and read device information	`target` (string, optional) BLE id or exact advertised name	`Switch2DeviceInfo`: `{ id, name, model, serial, hardwareRevision, softwareRevision, manufacturer, rssi }`
`disconnect_switch2`	Disconnect from the current Switch 2	none	`{ disconnected: true }`

Device state

Tool	Purpose	Parameters	Returns
`get_device_info`	Return cached model, serial, firmware, and manufacturer info	none	`Switch2DeviceInfo`
`get_status`	Sync clock, request analytics, and return decoded device status	`waitMs` (int, optional, 0-10000, default 3000) ms to wait for BLE notifications	Full `Switch2State`: status + presets + analytics + raw notifications
`get_presets`	Return cached presets for all 5 vapor profiles	none	Array of `Switch2Preset`: `{ preset, tempF, tempC, holdTime, heatingProfile, heatingProfileLabel, customProfile }`

Preset configuration

Tool	Purpose	Parameters	Returns
`set_active_preset`	Switch the active vapor profile	`preset` (int, required, 1-5)	`Switch2Status`
`set_preset_temperature`	Set a preset's target temperature	`preset` (int, required, 1-5); `tempF` (int, optional, 250-650) OR `tempC` (int, optional, 121-343). At least one is required.	Updated `Switch2Preset`
`set_preset_hold_time`	Set a preset's hold time	`preset` (int, required, 1-5); `holdTime` (int, required, 10-90 seconds)	Updated `Switch2Preset`
`set_heating_profile`	Set a preset's heating curve	`preset` (int, required, 1-5); `heatingProfile` (int, required): 161 Steady, 177 Ascent, 193 Descent, 209 Valley, 225 Hill, 241 Custom	Updated `Switch2Preset`

Session control

Tool	Purpose	Parameters	Returns
`start_session`	Start the active heating session	none	`Switch2Status`
`stop_session`	Stop the active heating session	none	`Switch2Status`
`extend_session`	Set the session extension value	`minutes` (int, required, 0-9)	`Switch2Status`

Device settings

Tool	Purpose	Parameters	Returns
`set_light_mode`	Set the LED pattern	`lightMode` (int, required, 0-17). 0=Stealth, 1=Calm, 2=Purple, 3=Blue, 4=Cyan, 5=Green, 6=Yellow, 7=Orange, 8=Red, 9=Pink, 10=Cali Sunset, 11=Purple Haze, 12=Northern Lights, 13=Vegas Nights, 14=Blue Dream, 15=Strawberry Cough, 16=Florida Groves, 17=Lime Light	`Switch2Status`
`set_light_brightness`	Set LED brightness	`brightness` (int, required, 0-100)	`Switch2Status`
`set_temp_unit`	Set displayed temperature unit	`tempUnit` (string, required): `"F"` or `"C"`	`Switch2Status`
`set_haptic_feedback`	Enable or disable haptic feedback	`enabled` (boolean, required)	`Switch2Status`
`set_auto_shutoff`	Set idle auto-shutoff timer. Use 0 to disable.	`minutes` (int, required, 0-60)	`Switch2Status`
`set_device_name`	Rename the Switch 2 (persisted on device)	`name` (string, required, 1-29 printable ASCII chars 0x20-0x7E)	`Switch2DeviceInfo`

Cleaning

Tool	Purpose	Parameters	Returns
`start_cleaning_assist`	Start the cleaning assist cycle	none	`Switch2Status`
`stop_cleaning_assist`	Stop the cleaning assist cycle	none	`Switch2Status`

Total: 21 tools.

Quick usage examples

Check device state and battery:

"Connect to my Switch 2 and tell me the battery level, current temperature, and active preset." The LLM calls connect_switch2 then get_status and reports back.

Change light and set temperature:

"Set preset 3 to 480F and switch the light to Purple Haze." The LLM calls set_preset_temperature with { preset: 3, tempF: 480 } and set_light_mode with { lightMode: 11 }.

Automated session:

"Start a session on preset 2, then stop it after I say done." The LLM calls set_active_preset with { preset: 2 }, then start_session, and waits for the next instruction to call stop_session.

Desktop control panel

A local web control panel is included under app/. It reuses Switch2Controller directly (no MCP layer) and serves a single-page UI at http://localhost:4477 over HTTP + Server-Sent Events. Controls mirror the official app: live temperature dial, preset editor, light mode and brightness, session start/stop/extend, cleaning assist, device rename, and all device settings.

# Real device
npm run app
# open http://localhost:4477

# Mock device (no hardware needed)
npm run app:mock

BLE protocol notes

Primary control surface:

Purpose	UUID
Demo service	`0000fee7-0000-1000-8000-00805f9b34fb`
Write characteristic	`0000fec1-0000-1000-8000-00805f9b34fb`
Notify characteristic	`0000fec2-0000-1000-8000-00805f9b34fb`
Device information service	`0000180a-0000-1000-8000-00805f9b34fb`

Intentionally excluded UUIDs:

Purpose	UUID
OTA service	`e5c7a653-7e52-4b06-af32-960455084ae3`
OTA write	`4cbbd40d-f1fa-4dbd-9bb5-36ec99d99a08`
OTA notify	`739cb17a-1aec-4232-a01a-a250d4c35f0d`

Safety boundaries

This server intentionally does NOT expose:

Firmware update or OTA writes
Factory reset
Arbitrary raw BLE writes

All state-changing tools validate input ranges before writing to the device. These boundaries are permanent design decisions, not omissions.

Verified device

Live verified on May 29, 2026:

Field	Value
BLE name	`My Switch 2`
Advertised service	`fee7`
Model	`Switch 2`
Serial	`SN-EXAMPLE-0000`
Hardware	`V2.0.0`
Firmware	`SW2-260322-010`
Manufacturer	`Dr.Dabber`

Development

npm test          # unit tests (21 tests)
npm run build     # compile TypeScript
npm run qa        # build + test
npm run probe     # BLE scan (requires hardware)
npm run live:status -- "My Switch 2"   # read-only live status

License

MIT

Available Tools

21 tools

connect_switch2Connect Dr Dabber Switch 2C

Connect to a Switch 2 and read device information.

Inputs: target.

disconnect_switch2Disconnect Dr Dabber Switch 2B

Disconnect from the current Switch 2.

Inputs: no named parameters.

discover_switch2Discover Dr Dabber Switch 2B

Scan for nearby Switch 2 devices advertising the fee7 BLE service.

Inputs: timeoutMs.

extend_sessionExtend SessionC

Set session extension value from 0 to 9.

Inputs: minutes (required).

get_device_infoGet Switch 2 Device InfoA

Return cached model, serial, firmware, and manufacturer information.

Inputs: no named parameters.

get_presetsGet Switch 2 PresetsA

Return cached preset temperatures, hold times, heating profiles, and custom points.

Inputs: no named parameters.

get_statusGet Switch 2 StatusB

Refresh and return current device status including battery, temperature, light mode, preset, and session state.

Inputs: waitMs.

set_active_presetSet Active PresetB

Set the active vapor profile preset from 1 to 5.

Inputs: preset (required).

set_auto_shutoffSet Auto ShutoffA

Set the device idle auto-shutoff timer in minutes from 0 to 60. Use 0 to disable auto-shutoff.

Inputs: minutes (required).

set_device_nameSet Device NameA

Rename the Switch 2. Accepts 1 to 29 printable ASCII characters (0x20-0x7E).

Inputs: name (required).

set_haptic_feedbackSet Haptic FeedbackC

Enable or disable haptic feedback.

Inputs: enabled (required).

set_heating_profileSet Heating ProfileC

Set preset heating profile. Values: 161 Steady, 177 Ascent, 193 Descent, 209 Valley, 225 Hill, 241 Custom.

Inputs: preset (required), heatingProfile (required).

set_light_brightnessSet Light BrightnessC

Set light brightness from 0 to 100.

Inputs: brightness (required).

set_light_modeSet Light ModeB

Set the active light mode from 0 to 17.

Inputs: lightMode (required).

set_preset_hold_timeSet Preset Hold TimeC

Set a preset hold time in seconds.

Inputs: preset (required), holdTime (required).

set_preset_temperatureSet Preset TemperatureC

Set a preset temperature. Provide either tempF or tempC.

Inputs: preset (required), tempC, tempF.

set_temp_unitSet Temperature UnitC

Set displayed temperature unit.

Inputs: tempUnit (required).

start_cleaning_assistStart Cleaning AssistD

Start cleaning assist.

Inputs: no named parameters.

start_sessionStart SessionC

Start the active heating session.

Inputs: no named parameters.

stop_cleaning_assistStop Cleaning AssistC

Stop cleaning assist.

Inputs: no named parameters.

stop_sessionStop SessionA

Stop the active heating session.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored 2026-06-27 19:15 across 21 tools

Disambiguation4/5

Most tools have clearly distinct purposes. However, set_active_preset, set_heating_profile, set_preset_hold_time, and set_preset_temperature all modify presets, potentially causing confusion about which preset is being affected and whether heating profile applies to active or specific preset.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., connect_switch2, get_device_info, set_light_mode). Naming is uniform and predictable across the entire set.

Tool Count4/5

With 21 tools, the count is slightly above the typical 3-15 range, but each tool corresponds to a distinct device feature or operation, so it is reasonable for a feature-rich device controller.

Completeness4/5

The tool surface covers connection, presets, sessions, lighting, cleaning, and various settings. Minor gaps like a factory reset or firmware update might exist, but the set is largely comprehensive for day-to-day device control.

Resources

Related MCP Connectors

hithereiamaliff-mcp-nextcloud
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
239
https://server.smithery.ai/@hithereiamaliff/mcp-nextcloud/mcp
mcp-klever-vmA
io.github.klever-io
MCP server for Klever blockchain smart contract development.
Blockchain Developer Tools Code Execution
16331
https://mcp.klever.org/mcp
mcpC
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
https://mcp.wix.com/mcp
jumpcloud-genai
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2
https://mcp.jumpcloud.com/v1

Related MCP Servers

MCP Server Example
Developer Tools Code Execution Autonomous Agents
alejandro-ao
A
license
B
quality
D
maintenance
An educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.
Updated 2 years ago (2025-04-29 10:58 UTC)
1
161
MIT
discord-mcp
Autonomous Agents Agent Orchestration Communication
SaseQ
A
license
Not graded
quality
B
maintenance
A Model Context Protocol (MCP) server for the Discord integration with MCP-compatible applications like Claude Desktop.
Updated 23 days ago (2026-10-23 17:22 UTC)
605
MIT
MCP Server Sample
Developer Tools Code Execution Autonomous Agents
antonscap
A
license
B
quality
D
maintenance
An educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.
Updated a year ago (2025-05-16 10:16 UTC)
2
MIT
MCP Server
Developer Tools App Automation
stelang
A
license
Not graded
quality
D
maintenance
An implementation of the Model Context Protocol (MCP) server that enables multiple clients to connect simultaneously and handles basic context management and messaging with an extendable architecture.
Updated a year ago (2025-06-08 03:44 UTC)
MIT

Dr. Dabber Switch 2 MCP

Problem it solves

Install

Option A: run from GitHub (no clone needed)

Option B: local clone

MCP client configuration

Direct BLE (laptop)

Pi BLE proxy (always-on headless path)

Environment variables

Transport

Complete tool reference

Connection

Device state

Preset configuration

Session control

Device settings

Cleaning

Quick usage examples

Desktop control panel

BLE protocol notes

Safety boundaries

Verified device

Development

License

Available Tools

Tool Schema Changelog

TDQS

Resources

Related MCP Connectors

Related MCP Servers

MCP Server Example

discord-mcp

MCP Server Sample

MCP Server