GS Robot MCP Server
Summary: This MCP server is an ops agent for Gausium cleaning robots, exposing 42 tools that read robot/fleet state, manage maps and tasks, control navigation, schedule work, and track reports — with dangerous tools gated behind user confirmation.
Fleet & robot status — list robots (paged, with
relationfilter), fetch battery/work-state snapshots for up to 100 SNs, decode work states locally, and check task capabilities (combined-task/schedule support).Maps & resources — list a robot's maps, fetch map canvas PNGs and grid metadata, list charging positions, and enumerate map/task resources (paths, regions, positions) — required before creating tasks or schedules.
Task definitions — list, get, create, update and delete task definitions (work mode, map resources, loop count, advance config).
Task execution — start, pause, resume, stop and skip items on a task; start returns
requestId/taskInstanceIdfor follow-up.Navigation — send a robot home, plus pause, resume and stop navigation.
Schedules — simple schedules (create/update/delete) and standard semester-style schedules (create/update/delete), plus read-only schedule listing, per-day details, monthly calendar and daily pre-tasks.
Commands & reports — check command delivery status, list command history, poll until a terminal status, and list task reports with their map images.
Workflow shortcut —
run_cleaning_taskbundles capabilities → resources → create → start → poll into one confirmed call.Local knowledge & memory —
lookup_error_coderesolves platform error codes from local tables, andremembersaves verified, reusable lessons to local memory (with user approval).Safety — every tool that moves a robot or writes data requires explicit confirmation (dangerous flag) before it reaches the machine; read-only tools like status, maps, and reports run freely.
Integrates with Gausium robots through the Gausium OpenAPI, providing tools for listing robots, fetching robot status, retrieving cleaning task reports, and accessing robot maps.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GS Robot MCP Server show me the status of my cleaning robot in the lobby"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An open-source ops agent for Gausium cleaning robots — MCP server, REST API, CLI and mobile web, on OpenAPI V3.
package mcp-gs-robot · pip install mcp-gs-robot
5-minute start · Let your AI agent set it up · Safety · Cognition & memory · Tools · HTTP API & H5 · Configuration · Troubleshooting · 中文文档
⚠️ Disclaimer — This is an unofficial, open-source project for personal research and learning. Not affiliated with, endorsed by, or supported by Gausium (高仙). Use at your own risk — robot commands move physical machines, so test on simulators or idle robots first. Built solely from the public Gausium OpenAPI V3 documentation.

The built-in H5 app, left to right: Home · Result cards · Execution pipeline · Robots · Current location. Running against a mock upstream with demo data.
What is this?
mcp-gs-robot wraps the Gausium OpenAPI V3 (robot status, maps, combined tasks, schedules, commands, reports) in a typed Python client, and exposes it through four entry points that share one tool registry:
Entry point | Command | Use it when… |
MCP Server (stdio) |
| Claude Code, Claude Desktop, Cursor, Cherry Studio or any MCP client should operate robots |
HTTP Server (FastAPI) |
| You want REST endpoints, Swagger and the built-in H5 mobile app |
Saodi 扫地僧 (CLI + H5 chat) |
| You want a chat assistant that plans and runs robot operations behind confirmation gates, and remembers what it learns |
Agent Skill |
| You want to teach Claude Code / Codex / WorkBuddy the correct operating procedure |
42 tools — all 36 V3 business endpoints, the legacy robot list, local lookups (
describe_work_state,lookup_error_code), local memory (remember) and workflow helpers (run_cleaning_task,wait_for_command)Typed & tested — pydantic v2 models, envelope unwrapping, upstream errors (6-digit platform codes, 10-digit robot task codes) surfaced as
GausiumAPIError; offline test suite with a mock HTTP transportSafety first — every tool that moves a robot or writes data is flagged
dangerousand needs explicit approval in the Agent, CLI and H5Gets smarter with use — sessions, tool calls and error threads are kept in a local SQLite file; verified lessons go into a private memory file that every new session loads
Provider-agnostic Agent — Anthropic (default,
claude-opus-5) or any OpenAI-compatible endpoint (DeepSeek, vLLM, Ollama…); it answers in the language you write inBuilt strictly on the official docs —
docs/apis.mdmaps each endpoint to its official page; the full contract isdocs/ARCHITECTURE_V3.md
Related MCP server: Eufy RoboVac MCP Server
5-minute quick start
Prerequisites: Python 3.12+, uv, and Gausium open-platform credentials (an application plus an AccessKey from the Gausium Developer Center). Node 18+ is only needed if you want to rebuild the H5 app — a production build is already committed.
1 · Install
git clone https://github.com/cfrs2005/mcp-gs-robot.git
cd mcp-gs-robot
uv sync --extra dev(Or pip install mcp-gs-robot if you only need the commands; the wheel ships the H5 build and the skill.)
2 · Configure — cp .env.example .env, then fill in:
What | Variables |
Gausium credentials |
|
Environment |
|
HTTP server key |
|
LLM (pick one) | Anthropic: |
.env is read from the current working directory by every entry point, is git-ignored, and must never be committed. Real environment variables take precedence over .env.
3 · Run an entry point (from the repository root)
Entry point | Command | Then |
MCP (stdio) |
| Ask your MCP client "List my robots and show battery and work state" |
REST + H5 |
| Open |
Saodi CLI |
| Chat in the terminal; dangerous steps ask |
Skill |
| Also mount the MCP server (row 1); the skill teaches the procedure |
Check that the server is up: curl -s http://127.0.0.1:8000/api/v1/health → {"status":"ok", …, "auth_required":true}. auth_required: true means the H5 needs the key before anything else works.
uv run saodi --show-context prints Saodi's full system prompt without any key — a quick way to confirm the install.
Let your AI agent set it up
Paste this into Claude Code, Codex or Cursor (agent mode). It installs, configures, tests and smoke-tests the project with read-only calls only. The same prompt, with a Chinese version, is in docs/AGENT_SETUP_PROMPT.md.
Set up mcp-gs-robot (an unofficial MCP / REST / agent wrapper for the Gausium OpenAPI V3) on this
machine. Work step by step, show me each command's result, and stop at the first failure.
Hard rules
- Robots are physical machines. Call read-only tools only. Never call a tool marked dangerous
(anything that creates, updates or deletes tasks or schedules, starts / pauses / resumes / stops /
skips tasks, navigates, runs a cleaning workflow, or writes memory with `remember`).
- Never print, echo, log or commit credentials. Write them only into .env with your file-edit tool
(not via shell echo), never paste them back to me, and confirm .env is git-ignored.
Steps
1. Prerequisites: `python3 --version` (3.12+) and `uv --version`. `node --version` (18+) only
matters for step 5.
2. `git clone https://github.com/cfrs2005/mcp-gs-robot.git && cd mcp-gs-robot && uv sync --extra dev`
3. `cp .env.example .env`. Ask me for GS_CLIENT_ID, GS_CLIENT_SECRET and GS_OPEN_ACCESS_KEY (the
AccessKeySecret, not the AccessKeyID), and whether to use production
(https://openapi.gs-robot.com/) or test (https://openapi.dev.gs-robot.com/) for GS_BASE_URL.
Ask which LLM provider I use: Anthropic (SAODI_PROVIDER=anthropic + ANTHROPIC_API_KEY) or an
OpenAI-compatible endpoint (SAODI_PROVIDER=openai + OPENAI_BASE_URL + OPENAI_API_KEY +
SAODI_MODEL). Generate GS_SERVER_API_KEY yourself with
`python3 -c "import re,secrets,pathlib;p=pathlib.Path('.env');p.write_text(re.sub(r'(?m)^GS_SERVER_API_KEY=.*$','GS_SERVER_API_KEY='+secrets.token_urlsafe(32),p.read_text()))"` (it rewrites the line in .env in place and never prints the key; I will read it from .env myself).
Then run `git check-ignore .env` (it must print .env) and `git status --short` (.env must not
appear).
4. `uv run pytest -q` and `uv run ruff check src tests`; both must pass.
5. If Node 18+ is available: `cd h5 && npm ci && npm run build && cd ..`. Otherwise skip; a
prebuilt H5 is already in src/gs_openapi/server/static/.
6. Start the server in the background with its output in a log file:
`uv run gs-robot-server > server.log 2>&1 &`
7. `curl -s http://127.0.0.1:8000/api/v1/health` must return "status":"ok" and
"auth_required":true.
8. Tell me to open http://localhost:8000/, go to Settings, paste the GS_SERVER_API_KEY value from
.env and press Save (it should report the connection as OK). Do not show me the key yourself.
9. Read-only smoke test. Load the key without printing it:
`KEY=$(grep '^GS_SERVER_API_KEY=' .env | cut -d= -f2-)`
- `curl -s -X POST -H "X-API-Key: $KEY" -H 'Content-Type: application/json'
-d '{"page":1,"page_size":5}' http://127.0.0.1:8000/api/v1/tools/list_robots`
- pick one robot from that list with "online": true and call get_robot_status the same way
with body {"robot_sn_list":["<that SN>"]}.
Error meanings: 401 = wrong or missing X-API-Key; 110003 = these credentials are not bound to
that robot (not "no data"); 230003 = robot offline; 100026 = rate limited, slow down.
10. Report: tool versions, pytest / ruff results, the health response, how many robots are
online / offline, and any error as `<code> <msg>`. Leave out secrets and trace IDs.Entry points in detail
From a clone (reads .env in the repository):
claude mcp add gs-robot -- uv --directory /path/to/mcp-gs-robot run mcp-gs-robotFrom pip install mcp-gs-robot, pass credentials explicitly — in claude_desktop_config.json / Cursor MCP settings:
{
"mcpServers": {
"gs-robot": {
"command": "mcp-gs-robot",
"env": { "GS_CLIENT_ID": "…", "GS_CLIENT_SECRET": "…", "GS_OPEN_ACCESS_KEY": "…" }
}
}
}Transport is stdio. MCP hosts run tools directly, so keep your host's own tool-approval prompts on for dangerous tools. Set GS_ENABLE_LEGACY_TOOLS=1 to also expose the 0.1.x tools as legacy_*.
uv run gs-robot-server # http://0.0.0.0:8000 (GS_SERVER_HOST / GS_SERVER_PORT)H5 app — open
http://localhost:8000/on your phone or in a browser, then fill in the API key under SettingsSwagger —
http://localhost:8000/docsDocker —
cp .env.example .env && $EDITOR .env && docker compose up -d(serves on:8000)
uv run saodi # provider and keys from .env
uv run saodi --robot <robot-sn> # scope the session to one robot
uv run saodi --show-context # print the system prompt and exit (no key needed)you> Is the lobby robot free? Enough battery for a full dust-push?
⚙ get_robot_status(robot_sn_list=["<robot-sn>"])
Online, 82% battery, IDLE on map "Lobby" — good to go.
you> Start the lobby dust-push task
⚙ list_task_definitions(...)
Approve start_task robot_sn=<robot-sn> fusion_task_id=…? [y/N] y
⚙ start_task(...) ⚙ wait_for_command(...)
Command delivered (cmdStatus=6); it is not finished yet — I'll check workState again in ~30 s.Other subcommands (no LLM key, no upstream calls):
uv run saodi memory # path and content of the local memory file
uv run saodi memory add "<lesson>" [--scope S] # add one lesson by hand
uv run saodi memory edit # open it in $VISUAL / $EDITOR
uv run saodi errors [--status open] [--json] # error threads from the tool-call log
uv run saodi errors show <id> # one thread with its recent calls
uv run saodi errors promote <id> # turn a thread into a memory lessonRenamed after 0.2.0: the old
pi-agentcommand andPI_AGENT_*variables still work for one release and print a deprecation warning.
cp -r skills/gs-robot ~/.claude/skills/gs-robot # Claude Code (user scope)
cp -r skills/gs-robot ~/.codex/skills/gs-robot # Codex CLIThe skill encodes the safe operating procedure (status → capabilities → resources → task definition → start → poll) and ships reference tables for work states, command types and task-start error codes. See skills/gs-robot/README.md.
Safety model
Tools that move a robot or write data are registered with dangerous=True. Saodi never runs them on its own: it emits confirm_required and waits — [y/N] in the terminal, buttons in the H5, POST …/confirm over REST. A rejected call never reaches the robot (or the memory file).
Keep in mind:
Delivered is not finished.
cmdStatus=6means the robot received the command; follow up withget_robot_statusor task reports.REST executes directly.
POST /api/v1/tools/{name}treats the caller as already having confirmed — gate it in your own client.SAODI_AUTO_APPROVE=1disables the Agent gate (not recommended).
For the common "clean these areas" case, run_cleaning_task bundles the whole procedure into one confirmed call:
Saodi's cognition and memory
Every new session gets one system prompt, assembled in this order and fixed for the session (saodi --show-context prints it):
Layer | Where | Maintained by | Shared? |
Soul — identity, voice (answers in your language), safety rules, when to propose |
| project maintainers | open source |
Knowledge — domain model, operating procedure, work-state table |
| project maintainers | open source |
Memory — field-tested call experience |
| contributors, via pull requests | open source |
Local memory — lessons learned on your machine |
| you and Saodi ( | private, never in git |
Private context — notes you keep elsewhere |
| you | private |
The official error-code table (skills/gs-robot/references/error-codes.md, ~23 KB) is not loaded into every prompt: Saodi calls the read-only lookup_error_code tool when it meets a code it does not know, and is told not to guess. The whole prompt is capped by SAODI_CONTEXT_MAX_CHARS (default 60000); when it overflows, the oldest local memory entries are dropped first and a WARNING says how many.
How it gets smarter
rememberin chat. When Saodi learns something verified and reusable — what an error code means in practice, a robot's lasting quirk, your preferences — it proposesremember(lesson). That writes a file, so it asks for confirmation like any dangerous tool. On approval it appends- [YYYY-MM-DD] lessontomemory.md; duplicates are skipped and anything that looks like a credential (token / secret / Bearer / long random strings) is refused. It does not remember one-off data (today's battery, a single snapshot) or guesses. The next session loads the new line.From errors to lessons. Every tool call is logged locally; failures are folded into error threads.
saodi errorslists them,PATCH /api/v1/errors/threads/{id}(try it in Swagger at/docs) lets you set the status, category and anote, andsaodi errors promote <id>writes the note (or, if empty, the category and sample message) intomemory.mdand marks the thread as promoted.By hand.
saodi memory add "…"orsaodi memory edit.Back to everyone. If a lesson is general, propose it for
experience.mdin a pull request. Writing rule: general behaviour and how to handle it only — no robot SNs, trace IDs, request IDs, accounts, credentials, customer or site names.
Tools
All 42 tools are defined once in gs_openapi/tools/ and exposed identically to MCP, the Agent and REST (POST /api/v1/tools/{name}). Inputs are snake_case; the registry maps them to V3 camelCase. ⚠️ = dangerous.
Category | Tools |
Robots |
|
Maps |
|
Tasks |
|
Schedules |
|
Commands |
|
Reports |
|
Workflows |
|
Reference |
|
Memory |
|
Robots & Maps
Tool | Required | Optional | Notes |
| – |
| Legacy |
|
| Adds | |
|
| Local lookup, no API call | |
|
| Combined-task / schedule support flags | |
|
|
| |
|
| Temporary PNG URL + grid metadata | |
|
| ||
|
|
| Resources without work modes |
|
|
| Query this before creating tasks/schedules |
Tasks
Tool | Required | Optional | |
|
| ||
|
|
| |
|
| ||
|
|
| ⚠️ |
|
| same as create | ⚠️ |
|
| ⚠️ | |
|
|
| ⚠️ returns |
|
| ⚠️ |
Schedules
Tool | Required | |
|
| ⚠️ |
|
| ⚠️ |
| standard schedule fields (see docs) | ⚠️ |
|
| |
|
| |
|
| |
|
|
Commands, Reports, Workflows, Reference & Memory
Tool | Required | Optional | |
|
|
| |
|
|
| |
|
|
| ⚠️ |
|
| ⚠️ | |
|
|
| |
|
|
| |
|
|
| Polls until a terminal |
|
|
| ⚠️ capabilities → resources → create → start → poll |
|
| Matching rows from | |
|
|
| ⚠️ appends |
Regenerate the list from the registry:
uv run python -c "from gs_openapi.tools.registry import REGISTRY; [print(t.category, t.name, '⚠️' if t.dangerous else '') for t in REGISTRY.values()]"HTTP API & H5
Base prefix /api/v1. GET /health is public; everything else requires X-API-Key when GS_SERVER_API_KEY is set. Errors share one envelope, {"error": {"code", "message", "trace_id"}}; upstream V3 errors become HTTP 502 carrying the business code.
Area | Routes |
Health & auth |
|
Tools |
|
Robots |
|
Maps |
|
Tasks |
|
Navigation |
|
Commands & reports |
|
Schedules |
|
Agent |
|
Error threads |
|
SSE events from /messages: text_delta · tool_call · tool_result · confirm_required · done · error. Sessions are stored in SQLite, so a conversation survives a server restart.
KEY=$(grep '^GS_SERVER_API_KEY=' .env | cut -d= -f2-)
SID=$(curl -s -XPOST -H "X-API-Key: $KEY" localhost:8000/api/v1/agent/sessions | jq -r .session_id)
curl -N -XPOST -H "X-API-Key: $KEY" -H 'Content-Type: application/json' \
-d '{"content":"List my robots and their battery"}' \
localhost:8000/api/v1/agent/sessions/$SID/messagesH5 (h5/, Vue 3 + Vite + Vant): Chat (a home screen with greeting, suggested questions and a fleet overview; streaming Markdown, HTML preview and mermaid diagrams; a tool-call timeline with result cards for robots, report KPIs, daily trends and maps; an execution pipeline card for dangerous tools — confirm → sent → delivered, nothing runs until approved; and a history drawer), Robots (fleet list with search and filters, online / offline / unreachable states, battery and work state), Detail (current location — the robot, its heading and map points on the map — maps & canvas, task definitions, quick actions, reports; offline robots get a banner instead of errors) and Settings (API base, API key, language). When the server needs a key and none is saved, the H5 sends you to Settings. The production build is committed to src/gs_openapi/server/static/, so pip install ships it.
Languages
H5: English and 中文, switchable under Settings → Language (the first visit follows the browser language).
Saodi: replies in the language you write in; field names such as
workStateorcmdStatusstay in English.Docs: English is the primary language; README_CN.md mirrors this file in Chinese. Tool descriptions are bilingual.
Configuration
Variable | Default | Description |
| – | Required. Gausium application + AccessKey credentials ( |
|
| Upstream base URL; test environment |
|
| HTTP timeout, seconds |
| unset |
|
|
| HTTP server bind |
| unset | When set, protected routes require |
|
|
|
|
| Model ID per provider |
| – | Anthropic provider key |
| – | OpenAI-compatible provider |
|
|
|
|
| Max tool cycles per user message (tool results are truncated at 20k chars) |
|
| Local data: |
| unset | Directory of private |
|
| System prompt length cap; oldest local memory entries go first, then truncation, with a WARNING |
Deprecated names, read for one more release when the new name is unset (each prints one WARNING with the name only):
New | Deprecated |
|
|
|
|
|
|
|
|
|
|
Troubleshooting
Symptom | Cause | Fix |
401 in the H5 or from curl |
| H5: Settings → paste the key → Save (it checks |
110003 | Your open-platform application is not bound to this robot (or lacks permission for this data) | This is not "no data". Check whether the SN appears in |
230003 | Robot offline / long disconnected from the cloud | Check |
100026 | Rate limit (~20 calls/s) | Slow down; avoid concurrent bursts |
422 with correct parameters | Possibly upstream field drift (the response no longer matches the local model) | Run |
Credentials "missing" although |
| Run commands from the directory holding |
| Old variable names in | Rename them to |
Development
src/gs_openapi/
├── auth/token_manager.py OAuth token (ms-epoch expiry, locked refresh)
├── core/ HTTP client, V3 endpoint registry, errors
├── v3/ GausiumV3 facade · pydantic models · reference tables
├── tools/ Tool registry (single source for MCP / Agent / REST) + knowledge tools
├── mcp/ FastMCP server (v3_server.py) + legacy_tools.py
├── agent/ Saodi core, soul.md, prompt builder, providers, sessions, CLI
├── store/ SQLite sessions / tool-call log / error threads, local memory.md
├── server/ FastAPI app, routes, SSE, static H5 hosting
└── main.py `mcp-gs-robot` stdio entry
h5/ Vue 3 mobile web app (builds into server/static)
skills/gs-robot/ Agent Skill + references (also Saodi's Knowledge / Memory)
docs/ARCHITECTURE_V3.md The contract every module follows
tests/ Offline tests (httpx.MockTransport, no network)uv sync --extra dev
uv run pytest -q
uv run ruff check src tests
cd h5 && npm ci && npm run build # rebuild the H5 into src/gs_openapi/server/static
uv build # wheel includes the H5 assets and the skillTo add a V3 tool, define the input model and handler in src/gs_openapi/tools/v3_tools.py with @tool(...); MCP, REST and the Agent pick it up automatically. Add a test and a row to the tool tables. Conventions are in CLAUDE.md; curl walkthroughs and MCP Inspector usage are in the Testing Guide.
0.1.x | 0.2.0+ |
|
|
|
|
|
|
|
|
|
|
Old tools remain available under legacy_* names with GS_ENABLE_LEGACY_TOOLS=1. The OAuth expires_in bug (a millisecond timestamp treated as seconds) is fixed, so remove any refresh workarounds.
Documentation
Document | Purpose |
Tool names, REST/SSE protocol, agent interface, cognition layers, local storage | |
Copy-paste prompt for Claude Code / Codex / Cursor (English + 中文) | |
Every endpoint with method, path, supported firmware and a link to the official page | |
MCP setup + Skill | |
Unit tests, curl walkthrough, MCP Inspector | |
Installing the skill in Claude Code / Codex / WorkBuddy | |
Release notes |
Contributing
Fork, create a feature branch, uv sync --extra dev, make your change with tests, run uv run pytest -q && uv run ruff check src tests, update the tool tables if you touched the registry, and open a pull request. Experience for experience.md is welcome — general behaviour only, with no SNs, trace IDs, accounts, credentials or customer / site names.
License
MIT — see LICENSE.
Disclaimer
This project is an unofficial, open-source effort for personal research and learning, built only from Gausium's public OpenAPI V3 documentation. It is not affiliated with, endorsed by, or supported by Gausium. No warranty of any kind; you are responsible for any robot you command. Always validate on simulators or idle machines first, keep credentials out of version control, and remember that a delivered command (cmdStatus=6) is not a completed task.
Made for people who would rather ask their robots than click through consoles.
Available Tools
42 toolscreate_scheduleD
创建标准排班 / Create schedule
Inputs: robot_sn (required), task_name (required), semester_type (required), plan_start_time (required), +13 more.
create_simple_scheduleD
创建简易排班 / Create simple schedule
Inputs: robot_sn (required), site_mode (required), task_name (required), work_mode (required), +13 more.
create_task_definitionD
创建任务定义 / Create task definition
Inputs: robot_sn (required), task_name (required), work_mode (required), map_resource_list (required), +3 more.
delete_scheduleD
删除标准排班 / Delete schedule
Inputs: robot_sn (required), plan_uuid (required), semester_uuid (required), operation_type (required), +4 more.
delete_simple_scheduleD
删除简易排班 / Delete simple schedule
Inputs: year (required), month (required), robot_sn (required), plan_uuid (required), +4 more.
delete_task_definitionD
删除任务定义 / Delete task definition
Inputs: robot_sn (required), fusion_task_id (required).
describe_work_stateC
解释工作状态 / Describe robot work state
Inputs: work_state (required).
get_command_statusC
查询命令投递状态 / Get command delivery status
Inputs: robot_sn (required), request_id (required).
get_map_canvasD
查询地图画布 / Get map canvas
Inputs: map_id (required), robot_sn (required).
get_robot_capabilitiesC
查询机器人任务能力 / Get task capabilities
Inputs: robot_sn (required).
get_robot_statusD
查询机器人状态 / Get robot status
Inputs: robot_sn_list (required).
get_scheduleD
查询排班详情 / Get schedule
Inputs: year (required), month (required), robot_sn (required), plan_uuid (required), +1 more.
get_schedule_calendarC
查询月度排班 / Get schedule calendar
Inputs: robot_sn (required), year_month (required).
get_task_definitionD
查询任务定义 / Get task definition
Inputs: robot_sn (required), fusion_task_id (required).
get_task_report_map_imagesD
查询报告地图图像 / Get report map images
Inputs: task_report_id (required), robot_sn.
list_charging_positionsC
列出充电点 / List charging positions
Inputs: map_id (required), robot_sn (required).
list_command_historyD
查询命令历史 / List command history
Inputs: robot_sn (required), page, pagesize, cmd_status, +1 more.
list_map_resourcesD
列出地图资源 / List map resources
Inputs: robot_sn (required), map_id_list (required), include_paths, include_regions, +1 more.
list_robot_mapsC
列出机器人地图 / List robot maps
Inputs: robot_sn (required).
list_robotsD
列出机器人 / List robots
Inputs: page, relation, page_size.
list_schedule_pre_tasksC
查询每日预任务 / List schedule pre-tasks
Inputs: date (required), robot_sn (required).
list_schedulesD
列出排班 / List schedules
Inputs: robot_sn (required).
list_task_definitionsC
分页查询任务定义 / List task definitions
Inputs: robot_sn (required), page, site_id, pagesize, +1 more.
list_task_reportsC
分页查询任务报告 / List task reports
Inputs: robot_sn (required), page, pagesize, end_time_max, +1 more.
list_task_resourcesD
查询任务资源 / List task resources
Inputs: robot_sn (required), map_id_list (required), include_paths, include_regions, +1 more.
list_work_modesD
查询工作模式 / List work modes
Inputs: robot_sn (required).
lookup_error_codeB
查询错误码含义与处置(本地码表与调用经验)/ Look up an error code's meaning and handling in the local reference tables
Inputs: code (required).
pause_taskC
暂停任务 / Pause task
Inputs: robot_sn (required).
rememberA
把一条经证实的可复用经验写入本地记忆(需用户确认)/ Save one verified, reusable lesson to local memory (needs user approval)
Inputs: lesson (required), scope.
resume_taskD
继续任务 / Resume task
Inputs: robot_sn (required).
run_cleaning_taskC
创建并启动清洁任务 / Create and start cleaning task
Inputs: map_id (required), robot_sn (required), task_name (required), resource_ids (required), +4 more.
skip_task_itemD
跳过任务项 / Skip task item
Inputs: robot_sn (required).
start_taskD
启动任务 / Start task
Inputs: robot_sn (required), fusion_task_id (required), loop_count.
stop_taskD
停止任务 / Stop task
Inputs: robot_sn (required).
update_scheduleD
更新标准排班 / Update schedule
Inputs: robot_sn (required), plan_uuid (required), semester_type (required), semester_uuid (required), +16 more.
update_simple_scheduleD
更新简易排班 / Update simple schedule
Inputs: year (required), month (required), robot_sn (required), plan_uuid (required), +16 more.
update_task_definitionD
更新任务定义 / Update task definition
Inputs: robot_sn (required), fusion_task_id (required), site_id, task_name, +4 more.
wait_for_commandC
等待命令投递终态 / Wait for command delivery
Inputs: robot_sn (required), request_id (required), timeout_seconds.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 42 tools
Many tools are distinct, but the simple-vs-standard schedule variants (create_simple_schedule vs create_schedule, etc.) are easy to confuse, and run_cleaning_task overlaps with create_task_definition plus start_task. Task, report, resource, and work-mode listing tools also have subtle boundary differences that descriptions only partially clarify.
Most names follow a consistent snake_case verb_noun pattern, such as list_robots, get_robot_status, create_task_definition, and stop_navigation. A few outliers like remember and wait_for_command are slightly less predictable, but the overall convention is stable.
With 42 tools, the surface is heavy for the apparent robot-management domain and exceeds the typical well-scoped range. The duplication of simple and standard schedule CRUD operations makes the set feel bloated rather than tightly scoped.
The server covers robot status, maps, task definitions and execution, reports, schedules, navigation control, command tracking, error lookup, and memory, which is broad lifecycle coverage. Minor gaps remain, such as no arbitrary point-to-point navigation tool, but core robot operations are well represented.
Maintenance
Related MCP Connectors
Control your Tesla from your AI assistant - climate, charging, access, and security.
Tesla data for your AI: battery, range, charging, tires, alerts, history. Controls off by default.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Tesla Fleet API for AI: send navigation destinations, read battery and location, run car commands.
Related MCP Servers
AlicenseBqualityDmaintenanceA 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.425MIT- 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.201,399 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to control a Cecotec Conga robot vacuum via 26 tools for state, cleaning modes, settings, timers, and system info.1-
- 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.-