Home Assistant MCP Server for LlamaIndex 15 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Home Assistant as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token — get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Home Assistant. "
"You have 15 tools available."
),
)
response = await agent.run(
"What tools are available in Home Assistant?"
)
print(response)
asyncio.run(main())
* 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.
LlamaIndex agents combine Home Assistant tool responses with indexed documents for comprehensive, grounded answers. Connect 15 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.
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 LlamaIndex 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 LlamaIndex via MCP
Follow these steps to integrate the Home Assistant MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 15 tools from Home Assistant
Why Use LlamaIndex with the Home Assistant MCP Server
LlamaIndex provides unique advantages when paired with Home Assistant through the Model Context Protocol.
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
Home Assistant + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Home Assistant MCP Server delivers measurable value.
Hybrid search: combine Home Assistant real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Home Assistant to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Home Assistant for fresh data
Analytical workflows: chain Home Assistant queries with LlamaIndex's data connectors to build multi-source analytical reports
Home Assistant MCP Tools for LlamaIndex (15)
These 15 tools become available when you connect Home Assistant to LlamaIndex via MCP:
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
Example Prompts for Home Assistant in LlamaIndex
Ready-to-use prompts you can give your LlamaIndex agent to start working with Home Assistant immediately.
"List all my smart home entities and show me the lights."
"Turn on the living room light and set it to 50% brightness."
"What is the current temperature in the bedroom and what mode is the thermostat?"
Troubleshooting Home Assistant MCP Server with LlamaIndex
Common issues when connecting Home Assistant to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpHome Assistant + LlamaIndex FAQ
Common questions about integrating Home Assistant MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect Home Assistant with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Home Assistant to LlamaIndex
Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.