xiaoi

xiaoi exposes multiple capabilities for controlling and interacting with Xiaoi speakers via an MCP server. The MCP server named xiaoi-mcp enables tools such as notify (send TTS notifications), play_audio (play a URL), set_volume, do_action (send MiOT commands), and get_property (read MiOT attributes). Each tool can optionally specify a target did (speaker) so you can route commands to a specific Xiaoi device, otherwise the server uses a default or configured speaker. This MCP integration makes it easy to orchestrate Xiaoi notifications from AI assistants, IDEs, or automation scripts, and to embed Xiaoi actions into larger workflows via standard MCP tooling.

Prerequisites:\n- Node.js >= 18 (Node.js 18.x or newer) and npm or pnpm\n- Access to the internet to install packages from npm registry\n\nInstall globally (recommended):\nbash\n# npm is recommended\nnpm i -g xiaoii\n\n# or pnpm (if you prefer)\npnpm add -g xiaoii\n\n\nAfter installation, you should have the xiaoi and xiaoi-mcp commands available system-wide. The MCP server component is exposed via the xiaoi-mcp CLI. You can verify installation by running:\nbash\nxiaoi --version\nxiaoi-mcp --version\n\n\nIf you prefer to install from source, clone the repository and install dependencies locally, then link the CLI tools:\nbash\ngit clone https://github.com/xvhuan/xiaoi.git\ncd xiaoi\nnpm install\nnpm link\n\nThis will make xiaoi and xiaoi-mcp available in your PATH.

Tips and common considerations:\n- Webhook authentication: When using the Webhook service, you can configure a token (webhook.token) and pass it in the Authorization header or X-Xiaoi-Token header for secure access.\n- Default speaker routing: If you omit did in a request, routing will follow the configured default speaker or environment variable XIAOI_DEFAULT_DID.\n- Configuration file: The config.json under ~/.xiaoi/config.json stores account, speaker, and webhook settings. Changes here affect how MCP commands resolve the target device.\n- Debugging: The MCP tools support optional did parameter to explicitly target a speaker. Use verbose logs in the config to help with troubleshooting.\n- Updates: The project frequently updates with new capabilities (e.g., additional MiOT actions, improved routing, and Webhook enhancements). Ensure your local installation is up-to-date to access new features.