MCP Server for Xiaozhi
The Home Assistant integration exposes selected tools to Xiaozhi so its voice agent can control permitted devices.
- 281 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The voice agent controls exposed devices and selected extra tools; an incorrect command can change the home’s state.
Install
- Works in
The author does not provide a one-line install. Open the repository and follow the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The voice agent controls exposed devices and selected extra tools; an incorrect command can change the home’s state.
This is third-party code. Review the repository files before installing.
What it does
MCP Server for Xiaozhi connects Home Assistant directly to a Xiaozhi endpoint over WebSocket. Users choose tool groups in the integration settings, allowing the voice agent to operate permitted home devices. Available actions depend on entities exposed to Home Assistant’s voice assistant. One connection can combine built-in Assist tools and additional MCP servers connected to Home Assistant. Multiple configured instances are supported. Installation uses HACS, and connection status appears on the Xiaozhi endpoint page.
Who it is for. Home Assistant owners using Xiaozhi who want to choose which devices and functions their voice assistant can access.
Good fit when
- Lights are already in Home Assistant and should be controlled through Xiaozhi.
- One voice connection needs several approved tool groups.
- Different Xiaozhi instances need separate configured connections.
- A failed voice command needs comparison with the Home Assistant log.
Not a fit when
- You need a documented connection from this server to Codex or Claude Code.
- The home must operate without contacting Xiaozhi servers.
- The selected device must not be controlled by a voice agent.
Example request
Check whether Xiaozhi can see the permitted office lamp and identify which tool it selected for the switch-on command.MCP
- Authentication
- not required
Limitations
Home Assistant with HACS is required. The integration opens an outbound WebSocket to Xiaozhi and does not provide a conventional local MCP launch for arbitrary clients. Available tools depend on the Home Assistant version and voice-exposed entities. The authors report conflicts between light or music control and Xiaozhi’s built-in behavior. By enabling extra MCP groups, users give the voice agent more actions; select only the devices and tools it needs.
How to disable. Disable MCP Server for Xiaozhi in Home Assistant and remove unnecessary voice-exposed entities.
FAQ
Where can I find the integration?
Search HACS for `xiaozhi` or `ha-mcp-for-xiaozhi`, download it and restart Home Assistant.
What should I select when adding it?
Find MCP Server for Xiaozhi under devices and services, then choose the Xiaozhi endpoint and required groups.
How do I check the connection?
Wait about a minute and refresh the Xiaozhi endpoint page to see its status.
Why is a device missing?
Check whether its entity is exposed to the Home Assistant voice assistant.
Where do I investigate a wrong command?
First inspect Xiaozhi’s chat history to see whether it selected a Home Assistant tool, then inspect the integration log.
Discussion
No questions or reviews yet.
Related
MCP serversA Node.js MCP server through which an agent controls Home Assistant devices and edits its automations
An MCP server for Home Assistant: the agent reads smart-home state and controls devices through your instance
MCP server for Home Assistant: an agent reads device states, controls them and edits smart home dashboards
A Home Assistant integration that puts GigaChat, YandexGPT or another LLM behind your smart-home voice assistant
Home Assistant Vibecode Agent
home-assistant-vibecode-agent
A Home Assistant add-on and MCP server: an agent checks the configuration and applies automations. A long-lived token is needed. Not an official project
MCP server for Yandex Smart Home with Alice: list devices, switch them on and off, power-cycle sockets and run scenarios
README in short
The README shows Home Assistant UI setup and the built-in Assist group. Its TV demonstration uses a custom script.