Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Home Assistant with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Control smart home devices and automations via Home Assistant REST API. lights, climate, media, covers, sensors, and more.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 15 capabilities

The complete Home Assistant capability set.

These are the exact actions your AI can choose when you ask it to work with Home Assistant.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 01

    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

  2. 02

    Get API status

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

  3. 03

    Get calendar events

    Get events from a Home Assistant calendar

  4. 04

    Get entity history

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

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 05

    List ha calendars

    List all calendars configured in Home Assistant

  2. 06

    Check ha configuration

    Check Home Assistant configuration validity

  3. 07

    Fire ha event

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

  4. 08

    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

Capability set03 / 04

09-12

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 09

    Get ha config

    Get the Home Assistant configuration details

  2. 10

    List ha components

    List all loaded components/integrations in Home Assistant

  3. 11

    List ha events

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

  4. 12

    Get logbook entries

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

Capability set04 / 04

13-15

3 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 13

    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

  2. 14

    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

  3. 15

    Render ha template

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

Observed, not estimated

896ms average. Fast in production.

Home Assistant is checked daily against the live service.

Daily averagePeak 949ms
Sep 1Today
Fastest day
896ms
Slowest day
949ms
14-day trend
Improving-6%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 15 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Home Assistant, so you can see the experience inside your AI.

It does not authenticate your account with Home Assistant. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Home Assistant Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_PFndzyBgm6EFRgWmvVvPuFq5L6pWhKzeDkkABGnT/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Home Assistant capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "home-assistant-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_PFndzyBgm6EFRgWmvVvPuFq5L6pWhKzeDkkABGnT/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Home Assistant owners ask.

  • 01

    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.

  • 02

    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.

  • 03

    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.

  • 04

    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.

Explore

More in Superpower

Suggestions