Home Assistant MCP Server
Control smart home devices and automations via Home Assistant REST API — lights, climate, media, covers, sensors, and more.
Ask AI about this MCP Server
Vinkius supports streamable HTTP and SSE.
* 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
What is the Home Assistant MCP Server?
The Home Assistant MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Home Assistant via 15 tools. Control smart home devices and automations via Home Assistant REST API — lights, climate, media, covers, sensors, and more. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.
Built-in capabilities (15)
Tools for your AI Agents to operate Home Assistant
Ask your AI agent "List all my smart home entities and show me the lights." and get the answer without opening a single dashboard. With 15 tools connected to real Home Assistant data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.
Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.
Why teams choose Vinkius
One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.
Build your own MCP Server with our secure development framework →Vinkius works with every AI agent you already use
…and any MCP-compatible client
Home Assistant MCP Server capabilities
15 toolsThis 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 Home Assistant configuration validity
The event type must match automation triggers configured in Home Assistant. Fire a custom event in Home Assistant
Use this as a connectivity test before making other API calls. Check if the Home Assistant API is running
Get events from a Home Assistant calendar
Useful for analyzing trends and past behavior. Get historical state data for an entity
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 the Home Assistant configuration details
Can be filtered by entity and time range. Get Home Assistant logbook entries
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
Each entity includes entity_id, state, last_changed timestamp, and attributes. Essential for discovering available devices. List all entity states in Home Assistant
List all calendars configured in Home Assistant
List all loaded components/integrations in Home Assistant
Useful for understanding what events Home Assistant is tracking. List all event types currently registered in Home Assistant
Useful for accessing HA template functions and state from the API. Render a Jinja2 template in Home Assistant
What the Home Assistant MCP Server unlocks
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
Frequently asked questions about the Home Assistant MCP Server
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.
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.
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.
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.
More in this category
Paperspace
6 toolsProvision and track powerful GPU workloads via Paperspace — list compute instances, fetch active deployments, trace team projects, and query Gradient environments via AI.
AT&T 5G
9 toolsAccess Open Gateway 5G Network APIs -- Number Verify, Device Location, SIM Swap detection, Quality on Demand, and Network Slicing via AT&T.
LangSmith (LLM Observability & Hub)
6 toolsMonitor LLM apps via LangSmith — track traces, audit prompt templates, and manage evaluation datasets.
You might also like
Sefaria Torah Texts API
5 toolsAccess sacred texts — audit Torah, Talmud, and library via AI.
CoinMarketCal
9 toolsEnable your AI agent to browse upcoming crypto events, listings, and forks via the CoinMarketCal API.
Aporia
7 toolsMonitor AI models and validate LLM interactions with guardrails directly from your AI agent to ensure safety and observability.
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.
Give your AI agents the power of Home Assistant MCP Server
Production-grade Home Assistant MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.