Ecovacs MCP Server

Created By
ecovacs-aia year ago
Ecovacs core API now fully supports the MCP protocol, making it the world's first robot service provider compatible with the MCP protocol. Ecovacs has completed the integration of 4 core API interfaces with the MCP protocol, including device list query, cleaning control, recharging control, and working status query. As the world's first cleaning robot service provider to support the MCP protocol, after the release of Ecovacs MCP Server, AI agent developers only need simple configuration to quickly access robot services in large language models, enabling query, cleaning, recharging, and other capabilities. This significantly lowers the threshold for calling robot control services during AI agent application development and greatly improves the development efficiency of AI agent applications.
Overview
{
    "mcpServers": {
        "ecovacs_mcp": {
            "command": "/Users/home/.local/bin/uv",
            "args": [
                "--directory",
                "/Users/home/ecovacs-mcp-main/ecovacs_mcp",
                "run",
                "robot_mcp_stdio.py"
            ],
            "env": {
                "ECO_API_KEY": "your AK...........",
                "ECO_API_URL": "https://open.ecovacs.com"
            }
        }
    }
}

Server Config

{
  "mcpServers": {
    "ecovacs_mcp": {
      "command": "/Users/home/.local/bin/uv",
      "args": [
        "--directory",
        "/Users/home/ecovacs-mcp-main/ecovacs_mcp",
        "run",
        "robot_mcp_stdio.py"
      ],
      "env": {
        "ECO_API_KEY": "your AK...........",
        "ECO_API_URL": "https://open.ecovacs.com"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ecovacs-ai
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago