Skip to main content
Glama
Sign In
anilsrml

roborock-mcp

by anilsrml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to roborock-mcp

No user-submitted related servers found.

    Related Servers

    • Roborock MCP server

      kerandia
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables controlling Roborock vacuums through MCP, exposing status, rooms, cleaning history, consumables, and robot controls.
      MIT

    • Roborock MCP Server

      Sathishkumar1805
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to control a Roborock vacuum via natural language, supporting commands like start, pause, dock, get status, and clean specific rooms.
      -

    • tuvio-vacuum

      yasg1988
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -

    • dreame-vacuum-mcp

      SarjuThakkar
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    • matic-desk-mcp

      pfduke02
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude, Codex, and other MCP clients to inspect a robot vacuum's status, rooms, bag estimate, history, and floor map, and to start, control, and configure local cleaning runs. Also supports recording bag swaps and saving room aliases through natural language.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct action on a distinct resource: device discovery, status, map, start, pause, and dock return. There is no meaningful overlap; the only nuance is that start_cleaning can resume a paused cleaning, which is explicitly documented.

    Naming Consistency5/5

    All six tools follow a strict verb_noun snake_case pattern (list_devices, get_status, get_map, start_cleaning, pause_cleaning, return_to_dock). No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for a vacuum control server, covering discovery, observability, and core cleaning commands without bloat or thinness. Each tool earns its place.

    Completeness4/5

    The cleaning lifecycle is essentially covered (list, status, map, start/resume, pause, dock), but there is no explicit stop_cleaning to end a job without docking, and no way to set fan speed or manage schedules/consumables. These are minor gaps an agent can work around by returning to dock.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources