ruru-swbot-mcp
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., "@ruru-swbot-mcp turn off the kitchen light"
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.
ruru-swbot-mcp
SwitchBot API の MCP サーバー。デバイスを名前で操作できる設計なので、AIがIDを間違えて操作を失敗するリスクがあんまりなかったりします。
インストール
npm install -g ruru-swbot-mcpRelated MCP server: HarmonyOS MCP Server
環境変数
SwitchBot アプリの設定からトークンとシークレットを取得し、設定してください。
変数名 | 説明 |
| SwitchBot API トークン |
| SwitchBot API シークレット |
MCP 設定
Claude Code
claude mcp add switchbot -- npx ruru-swbot-mcpClaude Desktop
{
"mcpServers": {
"switchbot": {
"command": "npx",
"args": ["ruru-swbot-mcp"],
"env": {
"SWITCHBOT_TOKEN": "<your-token>",
"SWITCHBOT_SECRET": "<your-secret>"
}
}
}
}リソース
リソース名 | URI | 説明 |
|
| 全物理デバイスの現在の状態(温度・湿度・電源など) |
ツール
ツール名 | 説明 |
| デバイス一覧を取得(名前・タイプ・利用可能コマンド) |
| デバイスの現在の状態を取得 |
| デバイスにコマンドを送信 |
| シーン一覧を取得 |
| シーンを実行 |
使い方の例
1. list_devices でデバイス一覧を確認
2. get_device_status({ deviceName: "リビング照明" }) で状態を取得
3. control_device({ deviceName: "リビング照明", command: "turnOn" }) で操作Available Tools
5 toolscontrol_deviceA
Send a command to a SwitchBot device by name. Use list_devices first to see available commands for each device. Examples: control_device({ deviceName: "リビング照明", command: "turnOn" }), control_device({ deviceName: "リビング照明", command: "setBrightness", parameter: "50" }), control_device({ deviceName: "リビング照明", command: "setColor", parameter: "255:0:0" })
Inputs: command (required), deviceName (required), parameter.
execute_sceneA
Execute a SwitchBot scene by name. Use list_scenes first to see available scenes. Example: execute_scene({ sceneName: "おやすみ" })
Inputs: sceneName (required).
get_device_statusA
Get the current status of a SwitchBot device by name. Returns power state, temperature, humidity, etc. depending on device type. Example: get_device_status({ deviceName: "リビング照明" })
Inputs: deviceName (required).
list_devicesA
List all SwitchBot devices with their names, types, and available commands. Use this first to see what devices you can control. Example response: [{"name": "リビング照明", "type": "Color Bulb", "commands": [{"command": "turnOn", ...}]}]
Inputs: no named parameters.
list_scenesA
List all SwitchBot scenes. Scenes are pre-configured automations that can control multiple devices at once. Example response: [{"name": "おやすみ"}, {"name": "おはよう"}]
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct action: listing devices, fetching device status, controlling a device, listing scenes, and executing a scene. There is no overlap or ambiguity between them, as the purpose of each is clearly separated.
All tool names follow a consistent verb_noun pattern: list_devices, get_device_status, control_device, list_scenes, execute_scene. The verbs are predictable and the nouns accurately represent the resource, making the naming convention uniform and intuitive.
With only 5 tools, the server is well-scoped for SwitchBot device and scene management. Each tool is necessary and covers a core operation, and the count is neither too sparse nor bloated for the intended functionality.
The tool surface covers the full lifecycle for both devices (list, get status, control) and scenes (list, execute). Since scenes are pre-configured automations, there is no need for create/update/delete of scenes, so the provided operations are complete for the domain.
Maintenance
Related MCP Connectors
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each device’s supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
Japanese catalog of physical devices AI agents can control: connectivity ratings, APIs, sources.
Connect AI assistants to Subotiz - Using Subotiz's external capabilities through natural language
Related MCP Servers
- AlicenseCqualityFmaintenanceEnables AI assistants to control SwitchBot devices, providing functionalities like device management, scene execution, and sensor information monitoring through the SwitchBot API.37ISC
- AlicenseBqualityDmaintenanceEnables AI assistants to control HarmonyOS devices, such as launching apps, through natural language.1635MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to directly interact with Matter devices and protocol operations, including device commissioning, attribute read/write, commands, and event monitoring, through natural language.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language control of Xiaomi smart home devices through MCP, focusing on homes, rooms, device names, and scenes without requiring protocol details.78MIT