Aqara MCP Server
Aqara smart home control via remote service endpoints for AI applications.
Data last scanned today · Reviewed today
Overview
The Aqara MCP Server enables AI applications to interact with Aqara smart home ecosystems. By configuring a remote MCP URL provided by the Aqara Agent, users can bridge their AI assistants with smart home hardware. The service supports a broad range of operations, including querying device status, managing scenes, controlling lighting effects, and monitoring energy consumption. It also facilitates firmware updates and automations across defined home and room spaces.
Our verdict
This server carries a high risk profile with a security score of 30/100. It is a community-maintained project rather than an official Aqara release, meaning it lacks the security oversight associated with vendor-backed tools. Furthermore, critical aspects such as the authentication method and read-only mode status remain unreviewed. Users should proceed with extreme caution and prioritize the official Aqara Agent Skills where possible.
- Operates with zero direct dependencies for reduced supply chain risk
- Includes comprehensive documentation in the repository
- Licensed under the permissive MIT license
- Community-maintained with no official vendor affiliation
- Critical security aspects like authentication remain unreviewed
- Bus-factor risk due to being maintained by a single contributor
Tools
| Tool | Description | Risk |
|---|---|---|
| all_homes_inquiry | Query all homes under the current Aqara account. | low |
| position_base_inquiry | Query basic information for all rooms/spaces in the current home. | low |
| device_base_inquiry | Query device basic information by room/space and device type, without real-time status. | low |
| device_status_inquiry | Query real-time device status such as power, brightness, color temperature, temperature, fan speed, and mode. | low |
| device_status_control | Control state or attributes of specified devices, such as power, brightness, color temperature, temperature, fan speed, mode, and curtain percentage. | medium |
| fuzzy_device_batch_control | Batch-control devices by room/space and device type. | medium |
| device_log_inquiry | Query device control logs within a time range, including control time, content, and result. | low |
| scene_base_inquiry | Query scene basic information, filterable by scene ID, position ID, or device ID. | low |
| scene_run | Run one or more specified scenes. | medium |
| scene_execution_history_inquiry | Query scene execution history within a time range. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What is the recommended alternative to configuring an MCP server for Aqara integrations?
If your application supports Agent Skills such as Cursor, Codex App, or OpenClaw, it is recommended to use official Aqara Agent Skills instead of manually configuring an MCP server.
›What prerequisites are needed to use the Aqara MCP server?
You need an Aqara account with registered smart devices, an application that supports remote MCP, and the API credentials obtained from the Aqara Agent login page.
›How do I authenticate my account for the MCP server?
Sign in with your Aqara account at the official Aqara Agent login page to generate your unique aqara_api_key and retrieve the required MCP URL.
›What is the typical URL for the remote MCP service?
The remote MCP URL for applications is typically https://agent.aqara.com/open/mcp.
›Are there specific security recommendations for handling my API key?
Yes, you must keep your aqara_api_key secure and avoid committing it to repositories, publishing it in screenshots, or sharing it with others.
Changelog
- Improvedv0.0.3
2026-04-17
- Improvedv0.0.2
2025-08-21
- Improvedv0.0.1
2025-05-30
- Improvedv0.0.1-alpha
2025-05-27
Badge
Maintain this server? Add the live badge to your README.