{"id":"ganhammar-hass-mcp-server","name":"hass-mcp-server","af_score":44.0,"security_score":49.8,"reliability_score":22.5,"what_it_does":"Provides a Model Context Protocol (MCP) server for Home Assistant using HTTP transport. It exposes MCP tools/resources/prompts/completions that let an AI assistant query Home Assistant state and call services, and it supports OAuth 2.0 authentication via an external OIDC server (hass-oidc-server), including dynamic client registration for remote use (e.g., Claude in a browser).","best_when":"You need agent-driven Home Assistant interaction over HTTP from outside the local network, and you can deploy/configure hass-oidc-server with appropriate OAuth/OIDC settings.","avoid_when":"You cannot properly secure OAuth/OIDC endpoints, don’t want to rely on experimental internal dashboard APIs, or you require strong documentation/contract guarantees beyond what’s described in the README.","last_evaluated":"2026-03-30T15:32:08.522021+00:00","has_mcp":true,"has_api":false,"auth_methods":["OAuth 2.0 (via OAuth endpoints provided by hass-oidc-server)"],"has_free_tier":false,"known_gotchas":["Dashboard create/update/delete tools are marked experimental and rely on internal Home Assistant APIs (DashboardsCollection), which may break with HA updates.","Many operations are side-effectful (create/update/delete automations/scenes/scripts/services). Without explicit idempotency/retry guidance, agents should be careful with duplicate requests.","OAuth/DCR flows add operational complexity; misconfiguration of hass-oidc-server can prevent the assistant from registering/authenticating successfully.","The README lists capabilities and example tool calls, but does not show exact MCP error formats/codes, so agent handling may require defensive fallbacks."],"error_quality":0.0}