Skip to main content
Glama
Sign In
auss

roomba-mcp

by auss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to roomba-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

    • irobot-mcp

      caffeinum
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to control a local-network iRobot Roomba over MQTT without cloud, including status monitoring, mission start/stop/pause/resume, docking, bin emptying, beeping, and plain-language error decoding.
      1
      MIT

    • 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

    • 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.
      -
    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

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    The set cleanly separates read tools (get_status, get_settings, get_map, get_consumables) from mission control (start/pause/resume/stop_clean) and config writes (set_setting, set_schedule, reset_consumable). Minor overlap exists between get_status and get_robot_info (both report robot state/capabilities), but the descriptions differentiate live state from identity/safety flags.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun pattern (get_status, start_clean, set_schedule, reset_consumable), with a consistent get_ prefix for reads. The lone bare verb 'dock' and the odd 'raw_publish' are small deviations but the overall pattern is readable and predictable.

    Tool Count4/5

    17 tools is on the heavier side but each maps to a genuine robot capability area (status, settings, schedule, maps, consumables, mission lifecycle, raw debug). Nothing appears duplicative, though the debug escape hatch is arguably extra surface.

    Completeness4/5

    The surface covers the full cleaning lifecycle, read-only telemetry, schedules, maps, settings, and consumable resets — a solid end-to-end picture. Gaps are minor: no map editing/region management beyond reading, and no targeted action like emptying the bin, but core workflows are reachable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources