A
licenseC
qualityB
maintenanceEnables AI assistants to control SwitchBot devices, providing functionalities like device management, scene execution, and sensor information monitoring through the SwitchBot API.
3
7
ISC
ruru-swbot-mcp
by arrow2nd
Related Servers
Alternatives to ruru-swbot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Home Assistant via natural language, including device control, automation management, and system monitoring.MIT
- 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
- AlicenseBqualityCmaintenanceEnables AI assistants to control HarmonyOS devices, such as launching apps, through natural language.1634MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language control of Xiaomi smart home devices through MCP, focusing on homes, rooms, device names, and scenes without requiring protocol details.68MIT
- AlicenseAqualityDmaintenanceEnables monitoring and control of SwitchBot devices (temperature sensors, plugs, bots) via Claude Desktop or Home Assistant.106 npmMIT
TDQS
A4.2/5.0
Scored across 5 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness5/5
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
ActivityInactive
ResponsivenessNo issues