Skip to main content
Glama
Sign In
arrow2nd

ruru-swbot-mcp

by arrow2nd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ruru-swbot-mcp

No user-submitted related servers found.

    Related Servers

    • matter-mcp-server

      MatterCoder
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly interact with Matter devices and protocol operations, including device commissioning, attribute read/write, commands, and event monitoring, through natural language.
      7
      MIT

    • 米家 MCP Server

      javen-yan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language control of Xiaomi smart home devices through MCP, focusing on homes, rooms, device names, and scenes without requiring protocol details.
      31 PyPI
      75
      MIT

    • switchbot-mcp

      PetitOnes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of SwitchBot devices such as plugs, lights, curtains, sensors, and infrared appliances through the SwitchBot Cloud API, including listing devices, checking status, sending commands, and turning power on or off.
      Apache 2.0
    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 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: listing devices, fetching device status, controlling a device, listing scenes, and executing a scene. There is no overlap or ambiguity between them, as the purpose of each is clearly separated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_devices, get_device_status, control_device, list_scenes, execute_scene. The verbs are predictable and the nouns accurately represent the resource, making the naming convention uniform and intuitive.

    Tool Count5/5

    With only 5 tools, the server is well-scoped for SwitchBot device and scene management. Each tool is necessary and covers a core operation, and the count is neither too sparse nor bloated for the intended functionality.

    Completeness5/5

    The tool surface covers the full lifecycle for both devices (list, get status, control) and scenes (list, execute). Since scenes are pre-configured automations, there is no need for create/update/delete of scenes, so the provided operations are complete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources