Skip to main content
Glama

Related Servers

Alternatives to Ecovacs MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      20
      599 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control devices via Tuya infrared remote control, supporting actions like toggling power and setting modes through natural language.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that enables AI assistants to discover, commission, and control Matter-compatible smart home devices through a standardized interface.
      8 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to control Xiaomi Mi Home smart devices through natural language, with support for listing devices, controlling properties, and running scenes.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      77
      72,385 PyPI
      4,855
      MIT

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_device_list retrieves robot information, get_work_state queries status, set_charging controls charging behavior, and set_cleaning manages cleaning operations. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear, descriptive names: get_device_list, get_work_state, set_charging, and set_cleaning. The naming convention is uniform throughout the set.

    Tool Count4/5

    With 4 tools, the count is reasonable for a robot vacuum control server, covering core operations like listing devices, checking status, and controlling charging and cleaning. It is slightly thin but functional for basic control.

    Completeness3/5

    The tools cover essential operations for robot vacuum control, but there are notable gaps such as missing update/delete functions for device management, scheduling capabilities, or advanced settings like cleaning modes. The surface is functional but not fully comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive