Xiaomi smart home MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIJIA_TOKEN | Yes | Access token obtained from login or API | |
| MIJIA_API_URL | Yes | The base URL of the mijia-control API server, e.g. http://127.0.0.1:5000/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | 列出所有米家智能设备。返回设备ID、名称、型号、在线状态等信息。 |
| get_deviceA | 获取设备详情,包含设备规格、可用属性列表和动作列表。 |
| get_propertyB | 读取设备属性值,例如灯光亮度、空调温度、开关状态等。 |
| set_propertyA | 设置设备属性值,用于控制设备。例如开灯、调亮度、设温度等。 |
| run_actionC | 执行设备动作,例如扫地机开始清扫、播放音乐等。 |
| list_scenesA | 列出所有米家场景。 |
| run_sceneC | 执行一个米家场景,触发该场景中预设的所有设备操作。 |
| list_homesB | 列出所有家庭及其设备概览。 |
| get_homeB | 获取家庭详情,包含该家庭下的所有设备列表。 |
| list_ble_devicesA | 列出所有已注册的蓝牙传感器设备,返回设备信息和最新温湿度读数。 |
| get_ble_sensorB | 获取蓝牙传感器的最新温湿度数据和设备详情。 |
| get_ble_readingsA | 查询蓝牙传感器的历史温湿度读数,用于趋势分析。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
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 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.
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.
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.