GS Robot MCP Server
Related Servers
Alternatives to GS Robot MCP Server
No user-submitted related servers found.
Related Servers
AlicenseBqualityFmaintenanceA control server that enables AI assistants to interact with Ecovacs robot vacuums through MCP protocol, supporting device listing, cleaning control, charging control, and status queries.423MIT- AlicenseBqualityDmaintenanceA Model Context Protocol server for controlling Eufy RoboVac vacuum cleaners, enabling users to scan for devices, connect to them, and execute various cleaning commands through natural language.20599 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of Tuvio/Tuya robot vacuum cleaners via a local hub, supporting commands such as start, pause, home, set mode, suction, water level, and more.-
- AlicenseNot gradedqualityBmaintenanceEnables control and monitoring of a Dreame robot vacuum via MCP tools, including cleaning, status, and map viewing through the cloud API.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables controlling Roborock vacuums through MCP, exposing status, rooms, cleaning history, consumables, and robot controls.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to control a Cecotec Conga robot vacuum via 26 tools for state, cleaning modes, settings, timers, and system info.1-
TDQS
Scored across 21 tools
Most tools have clear purposes, but there is notable overlap between download_robot_map_v1 and download_robot_map_v2, which differ only by API version and are easy for an agent to confuse. There is also potential ambiguity between the three workflow-execution tools and the lower-level task submission/command tools, since they cover overlapping workflows at different abstraction levels.
The tools mostly follow a consistent snake_case verb_noun pattern, such as list_robots, get_site_info, create_robot_command, and upload_robot_map_v1. The main deviations are the 'smart' suffix tools and nested workflow names like execute_s_line_site_task_workflow, but the pattern remains predictable overall.
With 21 tools, the surface is somewhat heavy for an MCP server, especially because several tools are version-specific or workflow-level wrappers around lower-level operations. The count is defensible for a broad robot management domain, but it feels closer to the upper limit of what a typical agent can navigate efficiently.
The toolset covers the core robot lifecycle well: robot listing, status, capabilities, map retrieval/upload, commands, task submission, reporting, and workflow execution. Minor gaps include lack of map update/delete operations and no v2 upload counterpart, but the available surface supports realistic automation workflows.