Home Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HA_URL | Yes | Your Home Assistant instance URL | |
| HA_TOKEN | Yes | Your Home Assistant long-lived access token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stateC | Get the current state of a Home Assistant entity |
| toggle_entityC | Toggle a Home Assistant entity on/off |
| trigger_automationC | Trigger a Home Assistant automation |
| list_entitiesC | List all available entities in Home Assistant |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_state retrieves entity status, list_entities enumerates available entities, toggle_entity changes binary states, and trigger_automation initiates automations. The actions (get, list, toggle, trigger) and targets (state, entities, entity, automation) are uniquely paired, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: get_state, list_entities, toggle_entity, and trigger_automation. The verbs are precise and descriptive, and the naming convention is uniform across all four tools, making them predictable and easy to understand.
With 4 tools, the count is slightly low but reasonable for basic Home Assistant control. It covers core operations like monitoring and toggling entities, and triggering automations, though it lacks advanced actions like setting specific states or managing scenes, which might be expected in a more comprehensive set.
The tool set covers essential read and toggle operations for entities and automations, providing a functional surface for basic interactions. However, there are minor gaps, such as the inability to set specific entity states (e.g., brightness or temperature) or manage other Home Assistant components like scenes or scripts, which could limit more complex agent workflows.