matic-desk-mcp
Related Servers
Alternatives to matic-desk-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to control a Roborock vacuum via natural language, supporting commands like start, pause, dock, get status, and clean specific rooms.-
- AlicenseNot gradedqualityCmaintenanceEnables controlling Roborock vacuums through MCP, exposing status, rooms, cleaning history, consumables, and robot controls.MIT
- FlicenseNot gradedqualityBmaintenanceEnables voice control of a Dreame robot vacuum via Matter using a Pebble Index ring, with tools for checking status, listing rooms and modes, starting/stopping cleaning, and docking.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to control a Cecotec Conga robot vacuum via 26 tools for state, cleaning modes, settings, timers, and system info.1-
- AlicenseBqualityCmaintenanceEnables MCP-compatible LLMs to control Amazon Alexa devices, including announcements, voice commands, smart-home group management, routines, media playback, and sensor state queries.32MIT
- AlicenseNot gradedqualityBmaintenanceEnables control and monitoring of a Dreame robot vacuum via MCP tools, including cleaning, status, and map viewing through the cloud API.5MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource or action: map/status/rooms/history/bag report, start/pause/resume/stop/dock, and settings/bag swap/room alias are clearly separated. The only close pair is stop vs dock, but their descriptions distinguish staying in place from returning home.
All tools use a consistent matic_ prefix and snake_case, with readable verb or noun phrases such as matic_start_cleaning, matic_pause, and matic_bag_report. No mixed casing or naming conventions appear.
13 tools is well-scoped for a robot vacuum control server, covering operation, state, history, bag maintenance, and room aliasing without obvious bloat.
Core robot lifecycle (start/pause/resume/stop/dock), status, map, rooms, settings, history, and bag management are covered. Minor gaps remain around scheduling, error clearing, and no-go zone management, but agents can work around them.