Skip to main content
Glama
Sign In
matic-desk-mcp

matic-desk-mcp

by pfduke02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to matic-desk-mcp

No user-submitted related servers found.

    Related Servers

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

    • 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

    • 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.
      -
    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.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: map/status/rooms/history/bag report, start/pause/resume/stop/dock, and settings/bag swap/room alias are clearly separated. The only close pair is stop vs dock, but their descriptions distinguish staying in place from returning home.

    Naming Consistency5/5

    All tools use a consistent matic_ prefix and snake_case, with readable verb or noun phrases such as matic_start_cleaning, matic_pause, and matic_bag_report. No mixed casing or naming conventions appear.

    Tool Count5/5

    13 tools is well-scoped for a robot vacuum control server, covering operation, state, history, bag maintenance, and room aliasing without obvious bloat.

    Completeness4/5

    Core robot lifecycle (start/pause/resume/stop/dock), status, map, rooms, settings, history, and bag management are covered. Minor gaps remain around scheduling, error clearing, and no-go zone management, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources