How to Use the Home Assistant MCP in Claude

Q: How do I install the Home Assistant MCP Server in Claude Desktop?

Open your claudedesktopconfig.json file from the developer settings. Add the server details to the mcpServers block and restart the application. You can also use the Extensions UI for a faster setup.

Q: Can Claude Desktop trigger my existing Home Assistant automations?

Yes, it triggers them via callhaservice. The client sends a request to the automation.trigger service with your specific entity ID. You do not need to rewrite the logic.

Q: How do I test my connection before writing prompts?

Run getapistatus to verify the REST API is responding. If that passes, use checkhaconfiguration to ensure your YAML files are valid.

Connect Claude Desktop to your local network and control your smart home devices directly from chat.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Home Assistant MCP to Claude Desktop

Create your Vinkius account to connect Home Assistant to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Home Assistant with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Command devices directly from your MCP Server

`call_ha_service` executes actions across your smart home domains. You tell your AI client to dim the living room lights or drop the thermostat, and it formats the exact JSON payload for the REST API. It handles the domain, service, and service data parameters without you digging through documentation. `get_entity_state` pulls current conditions before running a routine. The server reads the exact status of your locks, climate sensors, and switches. This lets Claude trigger the right `fire_ha_event` based on actual physical conditions in your house.

Analyze home history and sensor data

`get_entity_history` pulls past behavior for any registered device. Your agent reads temperature trends, motion sensor logs, and power consumption metrics over specific timeframes. You get exact timestamps and state changes instead of guessing when the HVAC kicked on. `get_logbook_entries` surfaces system events, while `list_ha_events` shows exactly what triggers your instance is currently tracking. Troubleshooting failed automations requires deep context. You debug complex routines right inside the chat interface.

Render Jinja2 templates on the fly

`render_ha_template` evaluates Jinja2 syntax against your live instance. You test complex logic and variable outputs before hardcoding them into your YAML files. The MCP server processes the template through the API and returns the exact string your automation will see. `list_available_services` dumps every valid action for your installed integrations, and `list_entity_states` grabs the current attributes for every device on your network. Exploring what your system can actually do takes seconds. You build automations based on what is actually running.

Setup guide

Set up Home Assistant MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Home Assistant MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Home Assistant MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under home-assistant-mcp.

json

{
  "mcpServers": {
    "home-assistant-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Home Assistant. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Home Assistant now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Home Assistant MCP in Claude Desktop

Open your claude_desktop_config.json file from the developer settings. Add the server details to the mcpServers block and restart the application. You can also use the Extensions UI for a faster setup.

Yes, it triggers them via call_ha_service. The client sends a request to the automation.trigger service with your specific entity ID. You do not need to rewrite the logic.

It works if your instance is publicly accessible. You paste the remote MCP URL into the Integrations settings in your browser. Localhost instances require the desktop app.

Run get_api_status to verify the REST API is responding. If that passes, use check_ha_configuration to ensure your YAML files are valid.

The server reads your sensor histories, lock states, and camera events via the REST API. Vinkius runs the connection in an ephemeral V8 Isolate Sandbox. Your API token never leaves the isolated environment, and the session terminates the moment you close the chat.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript