Home Assistant MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| homeassistant_apiB | Verify if the Home Assistant API is online |
| homeassistant_get_stateC | Get the state of a Home Assistant entity |
| homeassistant_call_serviceC | Call a service of a Home Assistant entity |
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 3 tools
Each tool has a clearly distinct purpose: one checks API status, one calls services, and one retrieves entity states. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent snake_case pattern with a 'homeassistant_' prefix and descriptive verb_noun combinations (api, call_service, get_state). This uniformity enhances readability and predictability.
With only 3 tools, the set feels thin for a Home Assistant integration, which typically involves more operations like listing entities, setting states, or handling events. While the tools cover basic needs, the scope could be expanded for better coverage.
The tools provide core functionality (API check, service calls, state retrieval) but lack operations like listing entities, updating states, or handling events. This creates minor gaps that agents might need to work around, though basic workflows are supported.