2,500+ MCP servers ready to use
Vinkius

Home Assistant MCP Server for Claude Code 15 tools — connect in under 2 minutes

Built by Vinkius GDPR 15 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add Home Assistant as an MCP server in one command and Claude Code will discover every tool at runtime — ideal for automation pipelines, CI/CD integration, and headless workflows via the Vinkius.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Home Assistant and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·bash
# Your Vinkius token — get it at cloud.vinkius.com
claude mcp add home-assistant --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
Home Assistant
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Home Assistant MCP Server

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.

Claude Code registers Home Assistant as an MCP server in a single terminal command. Once connected, Claude Code discovers all 15 tools at runtime and can call them headlessly — ideal for CI/CD pipelines, cron jobs, and automated workflows where Home Assistant data drives decisions without human intervention.

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)

The Home Assistant MCP Server exposes 15 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Home Assistant to Claude Code via MCP

Follow these steps to integrate the Home Assistant MCP Server with Claude Code.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using Home Assistant

Ask Claude: "Using Home Assistant, show me..."15 tools are ready

Why Use Claude Code with the Home Assistant MCP Server

Claude Code provides unique advantages when paired with Home Assistant through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly — no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using Home Assistant tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

Home Assistant + Claude Code Use Cases

Practical scenarios where Claude Code combined with the Home Assistant MCP Server delivers measurable value.

01

CI/CD integration: embed Home Assistant tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query Home Assistant nightly and generate reports without human intervention

03

Shell scripting: pipe Home Assistant outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query Home Assistant status endpoints and alert on anomalies

Home Assistant MCP Tools for Claude Code (15)

These 15 tools become available when you connect Home Assistant to Claude Code via MCP:

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

02

check_ha_configuration

Check Home Assistant configuration validity

03

fire_ha_event

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

04

get_api_status

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

05

get_calendar_events

Get events from a Home Assistant calendar

06

get_entity_history

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

07

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

08

get_ha_config

Get the Home Assistant configuration details

09

get_logbook_entries

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

10

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

11

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

12

list_ha_calendars

List all calendars configured in Home Assistant

13

list_ha_components

List all loaded components/integrations in Home Assistant

14

list_ha_events

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

15

render_ha_template

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

Example Prompts for Home Assistant in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with Home Assistant immediately.

01

"List all my smart home entities and show me the lights."

02

"Turn on the living room light and set it to 50% brightness."

03

"What is the current temperature in the bedroom and what mode is the thermostat?"

Troubleshooting Home Assistant MCP Server with Claude Code

Common issues when connecting Home Assistant to Claude Code through the Vinkius, and how to resolve them.

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Home Assistant + Claude Code FAQ

Common questions about integrating Home Assistant MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect Home Assistant to Claude Code

Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.