Switch Bot MCP Server

Follow the [Getting Started guide of SwitchBotAPI](https://github.com/OpenWonderLabs/SwitchBotAPI?tab=readme-ov-file#getting-started) to obtain the

Local serverstdio

What is the Switch Bot MCP server?

Follow the Getting Started guide of SwitchBotAPI to obtain the token and secret for SwitchBotAPI. That is what the switch bot mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • get_switch_bot_devices — Get SwitchBot devices
  • get_switch_bot_device_status — Get SwitchBot device status
  • execute_command — Execute a command on a device

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: SWITCH_BOT_TOKEN, SWITCH_BOT_SECRET, YOUR_SWITCH_BOT_TOKEN, YOUR_SWITCH_BOT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Switch Bot's toolset — get_switch_bot_devices, get_switch_bot_device_status, execute_command — is a fair guide to whether it matches your workflow. It is maintained by yasu89; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_switch_bot_devicesGet SwitchBot devices
get_switch_bot_device_statusGet SwitchBot device status
execute_commandExecute a command on a device

How to install the Switch Bot MCP server

{
  "mcpServers": {
    "switchbot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--name",
        "switch-bot-mcp-server",
        "-e",
        "SWITCH_BOT_TOKEN",
        "-e",
        "SWITCH_BOT_SECRET",
        "yasu89/switch-bot-mcp-server:latest"
      ],
      "env": {
        "SWITCH_BOT_TOKEN": "YOUR_SWITCH_BOT_TOKEN",
        "SWITCH_BOT_SECRET": "YOUR_SWITCH_BOT_SECRET"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SWITCH_BOT_TOKENCredential the server authenticates with.Yes
SWITCH_BOT_SECRETCredential the server authenticates with.Yes
YOUR_SWITCH_BOT_TOKENCredential the server authenticates with.Yes
YOUR_SWITCH_BOT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Switch Bot to get switch bot devices.
  • Use Switch Bot to get switch bot device status.
  • Use Switch Bot to execute command.

Frequently asked questions

It connects Switch Bot to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (get_switch_bot_devices, get_switch_bot_device_status, execute_command) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Switch Bot directly.