What Home Assistant URL should I use?

For local instances, use your Home Assistant's local network URL: `http://YOUR_IP:8123` (or `http://homeassistant.local:8123`). For cloud access via Nabu Casa, use your remote URL: `https://YOUR_INSTANCE.ui.nabu.casa`. The API is accessible at the same base URL as your Home Assistant frontend.

How do I get a Long-Lived Access Token?

Log in to your Home Assistant web interface, go to your user profile (click your name in the sidebar, then **Profile**), scroll down to **Long-Lived Access Tokens**, click **Create Token**, give it a name (e.g., 'MCP Server'), and copy the generated token. This token never expires unless manually revoked.

What devices and integrations are supported?

All Home Assistant integrations are supported since the API works at the service/state level. This includes lights (Philips Hue, LIFX, etc.), thermostats (Nest, Ecobee, etc.), covers/blinds, switches, media players (Sonos, Chromecast, etc.), sensors, cameras, locks, vacuums, and 1000+ other integrations. Use `list_entity_states` to discover all available entities.

Can I trigger Home Assistant automations from the API?

Yes! You can trigger automations in multiple ways: 1) Call the `automation.trigger` service directly, 2) Fire a custom event using `fire_ha_event` that matches an event trigger in your automation, 3) Call the `script.turn_on` service to run scripts. You can also control devices directly which will trigger related automations.

Home Assistant MCP Connector for Claude

A+

Control smart home devices and automations via Home Assistant REST API — lights, climate, media, covers, sensors, and more.

15 tools Official Updated Jun 28, 2026 Official Vinkius Partner

More Details Connect to Claude

Connect to your Home Assistant instance (local or Nabu Casa cloud) and control your entire smart home from any AI agent. Manage lights, climate, media players, covers, switches, and trigger automations via the Home Assistant REST API.

What you can do

Entity Discovery — List all entities and their current states across all integrations
Device Control — Turn lights on/off, adjust brightness, set thermostat temperatures, open/close covers
Service Calls — Call any Home Assistant service (light, switch, climate, cover, media_player, automation, script)
State Monitoring — Get real-time state of any entity including sensors, binary sensors, and device trackers
History & Logbook — Query historical state changes and logbook entries for analysis
Calendar Management — List and query calendar events from Home Assistant calendars
Event Automation — Fire custom events to trigger Home Assistant automations
Template Rendering — Render Jinja2 templates for advanced state access
Configuration — View system configuration, loaded components, and validate configuration
Local or Cloud — Works with local instances (http://IP:8123) or Nabu Casa cloud (https://INSTANCE.ui.nabu.casa)

How it works

Subscribe to this server
Enter your Home Assistant URL and Long-Lived Access Token
Start controlling your smart home from Claude, Cursor, or any MCP-compatible client

Your AI becomes a smart home assistant, helping you manage lighting, climate, media, and automations across your entire home.

Who is this for?

Smart Home Enthusiasts — control all Home Assistant-connected devices from AI assistants
Home Automation Builders — integrate HA into broader automation workflows and scripts
Property Managers — monitor and control devices across multiple properties
Energy-Conscious Users — optimize device states for energy savings via automations
Security-Conscious Users — monitor sensors, cameras, and alarm states remotely

smart-homehome-automationdevice-controllocal-controlautomation-triggers

15 tools expose this connector's capabilities to your AI agent.

get_api_status

Use this as a connectivity test before making other API calls. Check if the Home Assistant API is running

get_calendar_events

Get events from a Home Assistant calendar

list_ha_calendars

List all calendars configured in Home Assistant

check_ha_configuration

Check Home Assistant configuration validity

list_ha_components

List all loaded components/integrations in Home Assistant

get_ha_config

Get the Home Assistant configuration details

list_ha_events

Useful for understanding what events Home Assistant is tracking. List all event types currently registered in Home Assistant

get_entity_state

Use entity IDs from list_entity_states (e.g., light.living_room, climate.bedroom, sensor.temperature). Get the current state of a specific entity

get_entity_history

Useful for analyzing trends and past behavior. Get historical state data for an entity

get_logbook_entries

Can be filtered by entity and time range. Get Home Assistant logbook entries

render_ha_template

Useful for accessing HA template functions and state from the API. Render a Jinja2 template in Home Assistant

list_available_services

g., light: turn_on, turn_off, toggle; climate: set_temperature, set_hvac_mode). Essential for discovering what actions can be performed. List all available services across all domains

list_entity_states

Each entity includes entity_id, state, last_changed timestamp, and attributes. Essential for discovering available devices. List all entity states in Home Assistant

call_ha_service

This is the primary way to control devices in Home Assistant. COMMON SERVICE CALLS: - light.turn_on: entity_id, brightness (0-255), color_temp, rgb_color - light.turn_off: entity_id - switch.turn_on: entity_id - switch.turn_off: entity_id - climate.set_temperature: entity_id, temperature - climate.set_hvac_mode: entity_id, hvac_mode (heat, cool, auto, off) - cover.open_cover: entity_id - cover.close_cover: entity_id - media_player.turn_on: entity_id - media_player.turn_off: entity_id - media_player.media_play: entity_id - automation.trigger: entity_id - script.turn_on: entity_id DOMAINS: light, switch, climate, cover, fan, lock, media_player, automation, script, scene, input_boolean, input_number, notify PARAMETERS: - domain (REQUIRED): Domain name (e.g. light, switch, climate) - service (REQUIRED): Service name (e.g. turn_on, turn_off, set_temperature) - service_data (OPTIONAL): JSON object with service parameters including entity_id EXAMPLES: - "Turn on living room light" → domain="light", service="turn_on", service_data={"entity_id":"light.living_room"} - "Set bedroom temperature to 20" → domain="climate", service="set_temperature", service_data={"entity_id":"climate.bedroom","temperature":20} Call a Home Assistant service on a domain

fire_ha_event

The event type must match automation triggers configured in Home Assistant. Fire a custom event in Home Assistant

Related Connectors

PandaDoc MCP

10 tools Official

Create, send, and track documents, proposals, and e-signatures via PandaDoc — manage the entire document lifecycle from any AI agent.

A+ View details →

Jotform MCP

10 tools Official

Build powerful online forms with drag-and-drop ease, collect payments, gather signatures, and process submissions automatically.

A+ View details →

AudD Music Recognition MCP

8 tools Official

Universal music recognition — identify songs from URLs, search lyrics, and find streaming links via AI.

A+ View details →

Google Analytics MCP

12 tools Official

Query GA4 analytics data via Google Analytics API — run reports, check realtime data, analyze funnels, and export audiences directly from any AI agent.

A+ View details →