The SwitchBot MCP Server enables AI assistants to interact with and control SwitchBot devices. With this server, you can:
List available devices
Get device status (requires deviceId)
Control devices (turn on/off; requires deviceId and command)
Change device settings
Scene control (list and execute scenes)
Device status monitoring (temperature, humidity, brightness, motion)
Supported devices include Plugs, Bots, Curtains, Air Conditioners, Humidifiers, Lights, and Remote Controls.
Provides connectivity for SwitchBot devices which operate over Bluetooth, allowing device control for devices within Bluetooth range.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@SwitchBot MCP Server turn on the living room AC"
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.
This repository is archived and no longer maintained.
Please use the official SwitchBot implementation maintained by OpenWonderLabs:
npm install -g @switchbot/openapi-cli
switchbot auth login
switchbot mcp serveThe official MCP server supports stdio for local clients:
switchbot mcp serveIt also supports HTTP for a long-lived or remotely hosted agent worker:
switchbot mcp serve --port 8765For Codex or Claude Code, use the official setup commands documented upstream:
switchbot codex setup
switchbot claude-code setupIf browser authentication is not available, configure an API token and secret with:
switchbot config set-token <token> <secret>This repository is retained for historical reference only. Do not use its old package name, source-build instructions, or configuration examples for new deployments.
デバイスを制御します
Inputs: deviceId (required), command (required).
デバイスのステータスを取得します
Inputs: deviceId (required).
デバイス一覧を取得します
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: control_device performs actions on devices, get_device_status retrieves status information, and list_devices enumerates available devices. The descriptions clearly differentiate between controlling, checking status, and listing devices.
All three tools follow a consistent verb_noun pattern with snake_case naming: control_device, get_device_status, and list_devices. The naming is perfectly uniform and predictable across the entire tool set.
With only 3 tools, the count feels somewhat thin for a device control server that might benefit from more granular operations like specific device types or advanced controls. However, it covers the absolute basics adequately.
The tools provide basic CRUD-like coverage for device management (list, get status, control), but there are notable gaps such as no ability to create/configure new devices, delete devices, or handle device groups/scenes. The surface is functional but minimal.
Control your Tesla from your AI assistant - climate, charging, access, and security.
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
