HA Insights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HA_URL | No | Base URL of Home Assistant | http://localhost:8123 |
| HA_TOKEN | Yes | Long-lived access token (required) | |
| LOG_LEVEL | No | Log level; logs go to stderr | INFO |
| HA_TIMEOUT_SECONDS | No | Per-request timeout in seconds | 10 |
| HA_CACHE_TTL_SECONDS | No | Snapshot cache TTL in seconds (0 disables) | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_entitiesA | Find Home Assistant entities and their current states. |
| get_entity_stateA | Get the live state of one entity with its area, device and relevant attributes. The state is read fresh from Home Assistant. Attributes are filtered to the ones meaningful for the entity's domain (e.g. temperatures and modes for climate). |
| list_areasA | List all areas (rooms/zones) of the home with how many entities each contains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| home_summary | Compact overview of the home: areas with entity counts and entities per domain. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search_entities discovers entities, list_areas catalogs rooms/zones, and get_entity_state retrieves detail for a single entity. The descriptions explicitly guide sequencing from search to detail, leaving little room for misselection.
All tool names follow the same snake_case verb_noun pattern: search_entities, list_areas, get_entity_state. The convention is predictable and readable throughout.
Three tools is minimal but well-matched to this read-only Home Assistant insights server. Each tool serves a distinct discovery, area, or detail purpose, so none feels redundant or missing.
The surface covers the core read-only workflow: discover entities, understand areas, and inspect live entity state with relevant attributes. Minor gaps like a dedicated area-detail or history/statistics tool exist, but agents can work around them for the stated purpose.