Skip to main content
Glama
genm

SwitchBot MCP Server

by genm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SwitchBot MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Govee

      danjam
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
      9
      1
      MIT

    • mcp-mijia

      oujiafan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Xiaomi Mi Home smart devices through natural language, supporting device listing, property control, actions, and scenes.
      7
      MIT

    • Home Assistant MCP Server

      mjrestivo16
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.
      1
      MIT
    • Chirp Home Automation MCP Server by chirpwireless

      Chirp Home Automation MCPofficial

      chirpwireless
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI apps to securely connect to your Chirp home automation, letting you query sensors, control devices, manage automations, view alerts, and more through natural language.
      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

    C2.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: control_device performs actions on devices, get_device_status retrieves status information, and list_devices enumerates available devices. The descriptions clearly differentiate between controlling, checking status, and listing devices.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern with snake_case naming: control_device, get_device_status, and list_devices. The naming is perfectly uniform and predictable across the entire tool set.

    Tool Count3/5

    With only 3 tools, the count feels somewhat thin for a device control server that might benefit from more granular operations like specific device types or advanced controls. However, it covers the absolute basics adequately.

    Completeness3/5

    The tools provide basic CRUD-like coverage for device management (list, get status, control), but there are notable gaps such as no ability to create/configure new devices, delete devices, or handle device groups/scenes. The surface is functional but minimal.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources