Schema | hass-mcp

hass-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HASS_URL`	Yes	The URL of your Home Assistant instance (e.g., http://homeassistant.local:8123)
`HASS_TOKEN`	Yes	Your Home Assistant long-lived access token

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
ha_get_stateB	Get Home Assistant entity state by entity_id.
ha_list_statesA	List Home Assistant entity states (can be large).
ha_list_servicesA	List Home Assistant services and their fields.
ha_list_areasA	List Home Assistant areas from the area registry.
ha_list_devicesA	List Home Assistant devices from the device registry.
ha_list_entity_registryA	List Home Assistant entity registry entries.
ha_light_turn_onC	Turn on a light by entity_id.
ha_light_turn_offB	Turn off a light by entity_id.
ha_area_lights_offA	Turn off all lights in an area (by area_id).
ha_area_lights_onA	Turn on all lights in an area (by area_id).
ha_get_logbookA	Fetch logbook entries since an ISO time (optionally for an entity).
ha_get_historyC	Fetch history since an ISO time (optionally for an entity).
ha_call_serviceC	Call a Home Assistant service (domain/service) with data payload.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hannoeru/hass-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server