ruru-swbot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWITCHBOT_TOKEN | Yes | SwitchBot API トークン | |
| SWITCHBOT_SECRET | Yes | SwitchBot API シークレット |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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", ...}]}] |
| 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: "リビング照明" }) |
| control_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" }) |
| list_scenesA | List all SwitchBot scenes. Scenes are pre-configured automations that can control multiple devices at once. Example response: [{"name": "おやすみ"}, {"name": "おはよう"}] |
| execute_sceneA | Execute a SwitchBot scene by name. Use list_scenes first to see available scenes. Example: execute_scene({ sceneName: "おやすみ" }) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| device_statuses | All physical SwitchBot device statuses including temperature, humidity, power state, etc. |
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.