mcp_ha_xiaozhi

A Docker-deployable MCP proxy/service that connects “XiaoZhi (小智) official server” to a Home Assistant MCP server, using environment variables to specify the XiaoZhi MCP endpoint, the Home Assistant MCP server endpoint, and a long-lived Home Assistant access token.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ Automation mcp home-assistant docker python automation home-automation agent-integration

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

TLS is not explicitly stated in the provided README. Authentication appears to rely on a long-lived Home Assistant access token, likely with broad permissions; no evidence of fine-grained scopes or explicit MCP-level authorization controls in the provided content. Docker env var usage suggests operational convenience, but secret-handling practices (logging/redaction) are not documented here.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You already have Home Assistant’s MCP Server integration configured and you want a simple bridge to XiaoZhi’s MCP endpoint using Docker.

Avoid When

You need strong guarantees about interface stability, error semantics, rate limiting behavior, or documented authentication/authorization scope granularity beyond the provided token.

Use Cases

• Connect an XiaoZhi official MCP endpoint to Home Assistant’s MCP server via an intermediary MCP proxy
• Enable agents to control/query Home Assistant through MCP while originating from XiaoZhi’s side
• Bridge existing XiaoZhi example code to a Home Assistant MCP integration

Not For

• Direct interaction with Home Assistant’s REST API (it’s described as MCP-based proxying)
• Production deployments requiring well-specified, first-party API contracts (limited documentation provided here)

Interface

REST API

GraphQL

gRPC

MCP Server

SDK

Webhooks

Authentication

Methods: Long-lived Home Assistant access token (API_ACCESS_TOKEN)

OAuth: No Scopes: No

README indicates using a Home Assistant long-lived access token to authorize access to the Home Assistant instance. No OAuth or explicit MCP auth scheme details are provided in the provided content.

Pricing

Free tier: No

Requires CC: No

No pricing information provided in the supplied README/metadata.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ No documented MCP tool list, schemas, or error codes in the provided content; agent integration may require inspecting runtime behavior.
⚠ Token is a long-lived Home Assistant token; treat as high-privilege credential.
⚠ Rate limits and backoff/retry guidance are not described in the provided content.

Alternatives

Use Home Assistant’s MCP server integration directly with your agent/tooling Build a custom MCP proxy/gateway using official MCP libraries and Home Assistant integration primitives If available, use any vendor-supported MCP bridging/proxy solution for XiaoZhi and Home Assistant

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp_ha_xiaozhi.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.