An astronaut overseeing a futuristic data hub

Connect Home Assistant to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn your AI agent into a hands-on home manager.

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

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 15 capabilities

We ship only the actions that matter.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 01

    Call ha service

    This capability executes specific actions within Home Assistant domains like light, switch, or climate. Use it to turn devices on or off, set temperatures, or trigger scripts.

  2. 02

    Get API status

    This capability checks if your Home Assistant API is reachable. It is the first thing to run if you need to test your connection.

  3. 03

    Get calendar events

    This capability pulls event data from your configured Home Assistant calendars. It lets your agent know what is scheduled in your home.

  4. 04

    Get entity history

    This capability retrieves historical state data for a specific entity. Use it to analyze how a sensor or device has behaved over time.

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 05

    List ha calendars

    This capability returns a list of all calendars set up in your Home Assistant instance.

  2. 06

    Check ha configuration

    This capability validates your current Home Assistant configuration to ensure everything is set up correctly.

  3. 07

    Fire ha event

    This capability sends custom events to Home Assistant. It is used to trigger specific automations that listen for these events.

  4. 08

    Get entity state

    This capability fetches the current status of a specific entity. Use it to check if a light is on or what a temperature sensor currently reads.

Capability set03 / 04

09-12

4 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 09

    Get ha config

    This capability retrieves your Home Assistant configuration details.

  2. 10

    List ha components

    This capability lists all the integrations and components currently loaded in your system.

  3. 11

    List ha events

    This capability shows all the event types that Home Assistant is currently tracking.

  4. 12

    Get logbook entries

    This capability pulls entries from your Home Assistant logbook. You can filter these by entity or time to see what happened and when.

Capability set04 / 04

13-15

3 capabilities in this set.

Part of 15 available through Home Assistant.

  1. 13

    List available services

    This capability lists every service available across all your domains. It helps your agent discover what it can actually do, like toggling a switch or setting a scene.

  2. 14

    List entity states

    This capability provides a full list of all entities and their current states. It is the primary way for your agent to discover what devices are available.

  3. 15

    Render ha template

    This capability runs Jinja2 templates within Home Assistant. Use it when you need to perform complex state calculations or logic.

Real work

What teams actually run

01

Daily Routines

Ask your agent to prepare the house for bed by turning off lights and locking doors in one go.

02

Climate Management

Tell your agent to set the bedroom to a specific temperature when you are heading home.

03

Security Monitoring

Ask your agent to check the status of all motion sensors or door locks if you feel uneasy.

04

Energy Optimization

Use the agent to check which devices are drawing power or to turn off unused electronics.

Automate a task

Put Home Assistant to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Home Assistant works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Home Assistant to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

938ms average. Fast in production.

Home Assistant is checked daily against the live service.

Daily averagePeak 1206ms
Oct 3Today
Fastest day
803ms
Slowest day
1206ms
14-day trend
Improving-18%

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

Guided setup for Claude? Set up Home Assistant in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Home Assistant owners hand off.

This MCP is built for anyone who wants to move beyond manual app toggling and use natural language to manage their environment.

  • 01

    Smart Home Enthusiasts

    People who want to control their entire device ecosystem through a single AI interface.

  • 02

    Home Automation Builders

    Users who want to integrate their existing HA automations into broader AI-driven workflows.

  • 03

    Property Managers

    Professionals who need to monitor and control devices across multiple different properties.

FAQ

Questions Home Assistant owners ask.

  • 01

    Does this work with local Home Assistant installs?

    Yes. You can connect to a local instance using your local IP address or via Nabu Casa cloud.

  • 02

    What do I need to connect this MCP?

    You will need your Home Assistant URL and a Long-Lived Access Token generated from your Home Assistant profile.

  • 03

    Can I control any device in my house?

    If the device is integrated into Home Assistant and has an associated entity, your agent can control it using service calls.

  • 04

    How does the AI know which lights I have?

    The agent uses the list_entity_states capability to discover all available devices and their current statuses.

  • 05

    Is my data secure?

    The MCP uses your provided Long-Lived Access Token to communicate with your instance, following standard Home Assistant security protocols.

  • 06

    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.

  • 07

    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.

  • 08

    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.

  • 09

    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.

Connect Home Assistant to Claude, Cursor, ChatGPT & more