Skip to main content
Glama
Sign In
Xiaomi smart home MCP server

Xiaomi smart home MCP server

by handsomejustin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Xiaomi smart home MCP server

  • Home Assistant MCP

    hpohlmann
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol (MCP) integration that allows AI assistants to control Home Assistant devices by searching for entities and controlling devices through natural language commands.
    3
    24
    MIT

  • Home Controller

    winsthuang
    A
    license
    Not graded
    quality
    D
    maintenance
    A unified smart home automation system that enables control and monitoring of Miele appliances, LG ThinQ devices, HUUM saunas, and Phyn water monitors through Claude using the Model Context Protocol.
    26 npm
    MIT

  • mihome-mcp

    mizuka-wu
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server based on the Mastra framework for controlling Xiaomi Mi Home smart devices. It enables device discovery, property management, action execution, and scene control through the Mi Home cloud service.
    ISC

Related Servers

  • Hermejia

    HuishanLi1997
    A
    license
    Not graded
    quality
    D
    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

  • miloco-mcp-server

    toddpan
    A
    license
    Not graded
    quality
    C
    maintenance
    A local MCP server that lets AI assistants list and control home devices — lights, air conditioners, cameras, speakers, plugs and scheduled tasks — across Xiaomi (Mi Home), Tuya, Midea, eWeLink (Sonoff) and Huawei SmartHome using accounts you authorize on your own machine. It binds to localhost only and communicates with each vendor cloud, so agents can act on devices through natural language.
    33 npm
    2
    MIT

  • miot-mcp

    oadank
    A
    license
    Not graded
    quality
    C
    maintenance
    A productized MCP server for Xiaomi Mi Home (米家) that provides natural-language-oriented device discovery and control across homes, rooms, devices, and scenes, while hiding low-level protocol details like did/siid/piid. It supports QR login, structured tooling for status, brightness, temperature, scenes, and speaker announcements, plus standard MCP resources.
    1
    MIT

  • xiaomi-device-control

    alleneee
    F
    license
    Not graded
    quality
    D
    maintenance
    MCP server for controlling Xiaomi/Mi Home smart devices via natural language, supporting device listing, property read/write, action calls, and camera snapshots.
    12
    -

  • mcp-xiaomi-server

    ganyu123456
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables control of local Xiaomi smart home devices via MCP, allowing reading real-time status and setting properties through natural language, without relying on the Xiaomi cloud.
    MIT

  • oh-my-sage-mcp

    allocnode
    A
    license
    Not graded
    quality
    A
    maintenance
    An MCP server that enables natural language creation and management of Xiaomi Mi Home automation rules, integrating with AI coding assistants to query devices and manipulate automation graphs.
    124
    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

A3.5/5.0

Scored across 12 tools

Disambiguation4/5

Tools are largely distinct by resource: devices, scenes, homes, and BLE sensors. However, get_device, get_property, and get_ble_sensor could be confused for retrieving device info, but descriptions clarify their specific focus (details vs. property vs. BLE sensor). Overall, minimal overlap.

Naming Consistency4/5

Naming follows a consistent verb_noun pattern for most tools (list_devices, get_device, set_property, run_scene, etc.). Minor deviations: 'get_ble_readings' uses a different plural form but still fits the pattern. Overall, the pattern is clear and predictable.

Tool Count5/5

With 12 tools, the server covers a reasonable scope for a smart home integration. Each tool serves a distinct function, and the count is within the ideal range, not excessive or insufficient.

Completeness4/5

The surface covers device listing/detail, property read/write, actions, scenes, homes, and BLE sensor data. Missing are device creation/removal (likely not applicable for a smart home) and maybe a bulk operation or scene creation/update. However, the core control workflows are well covered, with minor gaps for advanced management.

Maintenance

ActivityNo data
ResponsivenessSyncing

Resources