Home Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASS_HOST | Yes | Your Home Assistant URL (e.g., https://your-instance.ui.nabu.casa) | |
| HASS_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 |
|---|---|
| list_entitiesB | List all Home Assistant entities (lights, switches, sensors, etc.) |
| get_entity_stateC | Get the current state and attributes of a specific entity |
| call_serviceC | Call a Home Assistant service (e.g., turn on a light, set climate) |
| list_servicesB | List all available Home Assistant services |
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: call_service performs actions, get_entity_state retrieves specific entity data, list_entities enumerates all entities, and list_services enumerates all services. The descriptions make it unambiguous which tool to use for each operation.
All tools follow a consistent verb_noun pattern (call_service, get_entity_state, list_entities, list_services) with clear, descriptive names. The naming convention is uniform throughout the set, making it easy to predict tool functions.
With 4 tools, the count is appropriate for a Home Assistant server, covering core operations like querying and controlling entities. It might be slightly lean for advanced workflows (e.g., missing event listening or configuration tools), but it's well-scoped for basic automation tasks.
The toolset covers essential CRUD-like operations for Home Assistant: listing and getting entities, and calling services. A minor gap exists in not providing tools for entity creation/deletion or event handling, but agents can perform core tasks effectively with the available tools.