Labsco
MCP SERVER

Ecovacs Robot Control

by ecovacs-ai

Tell a robot vacuum by name to start cleaning, pause, go back to the dock, or say what it is doing.

IoT, Smart Home & Embedded Hardware
Summary
Cleaning as something an assistant can start, stop and check on.

List, clean, dock, status is the whole surface, and it covers what people actually ask for. The status read is more detailed than the four operations suggest, because it distinguishes drying mops from collecting dust from genuinely idle.

What it is

The official Ecovacs robot-control server. Four core Ecovacs API endpoints are exposed as tools: the list of robots bound to your account, cleaning control, return-to-dock control, and a working-status read. Robots are addressed by nickname, with fuzzy matching.

What you get
  • Every robot bound to your account, returned by nickname
  • Cleaning started, resumed, paused or stopped, through the act values s, r, p and h
  • Return-to-dock started or stopped, through go-start and stopGo
  • A status read returning cleanSt for what it is doing, including cruising, map-building and pet-finding states
  • chargeSt for charging state, distinguishing heading back, idle, dock charging and cable charging
  • stationSt for the base station: washing mops, drying, dust collection or cleaning itself
Requirements

Pip install ecovacs-robot-mcp, or clone the repository and run it under uv. Set an API key for access, and point the server at the API host for your region, https://open.ecovacs.cn inside mainland China and the international host outside it.

Setup effort

One command plus a key — pip install ecovacs-robot-mcp, then supply credentials