4,000+ servers built on MCP Fusion
Vinkius
LlamaIndexFramework
LlamaIndex
Why use Home Assistant MCP Server with LlamaIndex?

Bring Smart Home
to LlamaIndex

Create your Vinkius account to connect Home Assistant to LlamaIndex and start using all 15 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Call Ha ServiceCheck Ha ConfigurationFire Ha EventGet Api StatusGet Calendar EventsGet Entity HistoryGet Entity StateGet Ha ConfigGet Logbook EntriesList Available ServicesList Entity StatesList Ha CalendarsList Ha ComponentsList Ha EventsRender Ha Template
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Home Assistant

What is the 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.

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

  1. Subscribe to this server
  2. Enter your Home Assistant URL and Long-Lived Access Token
  3. 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

Built-in capabilities (15)

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

check_ha_configuration

Check Home Assistant configuration validity

fire_ha_event

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

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

get_entity_history

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

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_ha_config

Get the Home Assistant configuration details

get_logbook_entries

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

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

list_ha_calendars

List all calendars configured in Home Assistant

list_ha_components

List all loaded components/integrations in Home Assistant

list_ha_events

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

render_ha_template

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

Why LlamaIndex?

LlamaIndex agents combine Home Assistant tool responses with indexed documents for comprehensive, grounded answers. Connect 15 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine Home Assistant tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain Home Assistant tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query Home Assistant, a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what Home Assistant tools were called, what data was returned, and how it influenced the final answer

L
See it in action

Home Assistant in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Home Assistant with Vinkius?

The Home Assistant connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 15 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

Home Assistant
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Home Assistant using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Home Assistant and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Home Assistant to LlamaIndex through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Home Assistant for LlamaIndex

Every request between LlamaIndex and Home Assistant is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

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.

05

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

06

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Home Assistant tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

07

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

08

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →