Home Assistant MCP. Control your whole smart home with conversation.
Home Assistant MCP connects your smart home ecosystem—lights, thermostats, media players, and sensors—to any AI agent. Use natural language prompts to monitor device status or run complex automations across local or cloud-based Home Assistant instances.
Give Claude and any AI agent real-world access
The agent lists all connected smart home components and tells you their current operating state.
You can tell the system to change settings, like setting a thermostat temperature or dimming lights.
The agent runs predefined automations and sends custom events through your home network.
You can list or query scheduled events stored in Home Assistant calendars.
Ask an AI about this
Waiting for input…
What AI agents can do with Home Assistant MCP: 15 Tools for Automation
These tools let you list device states, adjust temperatures, run automations, and track system logs across your connected smart home.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Home Assistant MCPGet Api Status
Run a quick test to confirm the Home Assistant API is online and ready for commands.
Get Calendar Events
Retrieves scheduled events from any calendar linked in your system.
List Ha Calendars
Shows all the individual calendars configured within Home Assistant.
Check Ha Configuration
Validates the overall configuration of your Home Assistant system for errors.
List Ha Components
Lists all major integrations and components that are currently running in Home...
Get Ha Config
Retrieves detailed information about the overall system configuration settings.
List Ha Events
Shows every type of custom event that is actively tracked by your Home Assistant setup.
Get Entity State
Checks the current status of one specific device or sensor using its unique ID.
Get Entity History
Gathers historical data points for a single entity, helping you analyze usage...
Get Logbook Entries
Retrieves a chronological list of significant activity entries and system logs.
Render Ha Template
Executes complex template code using Jinja2 to calculate or format advanced state...
List Available Services
Displays a comprehensive list of all actions (services) that can be performed across every device domain.
List Entity States
Lists the current state, last change time, and attributes for every connected entity.
Call Ha Service
The main function: it executes any specific service call, like turning on a light or...
Fire Ha Event
Sends a custom, triggered event to initiate automations elsewhere in the system.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Home Assistant, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The pain of manually checking every smart device dashboard.
Right now, if you need to know why the bedroom light is dim and if the thermostat was working correctly yesterday, you have to open three different apps. You check the lights app for brightness, then switch over to the climate control page to see mode details, and finally jump into a logbook just to verify when the last change happened. It’s constant context switching and clicking.
With this MCP, your agent handles it all in one go. You ask, 'What was the activity status of the bedroom zone?' The agent uses its tools—like `get_entity_state` and `get_logbook_entries`—to gather the data points and present you with a single, cohesive answer.
The Home Assistant MCP gives you control over your entire physical environment.
You never have to manually write out specific service calls or worry about the correct JSON structure for every domain. You don't need to remember if a light uses `light.turn_on` or another service call; you just ask your agent, and it figures out the proper parameters using tools like `list_available_services`.
It changes everything. Your AI client moves from being a helpful chatbot into an actual operational controller for your physical world.
What Home Assistant MCP does for your AI
Connecting your entire smart house to an AI client is simple. This MCP lets you use conversation to manage everything from turning lights on and off to adjusting the climate temperature.
Your agent talks directly to your home's central hub via the REST API. You can ask it what the current humidity level is, check if a specific door sensor was tripped, or even tell it to run an entire automation sequence—all without opening a single app dashboard. It’s like having a dedicated smart home professional that lives inside your AI workflow.
If you're building complex systems and need reliable connections across multiple platforms, Vinkius provides the central point where your agent can talk to thousands of services, making this connection effortless. You get real-time data on every entity, history logs for troubleshooting, and control over specific devices—all from one prompt.
019d75b2-2025-7317-b1a6-1921f44380ac How to set up Home Assistant MCP
The bottom line is that it translates natural language commands into precise smart home actions.
Connect your Home Assistant instance URL and a long-lived access token to this MCP.
Tell your AI agent what you want done, for example: 'Set the living room lights to 50% brightness.'
Your agent sends the specific service command through the API, updating your physical devices in real time.
Who uses Home Assistant MCP
This MCP is for anyone whose job involves managing a physically automated environment. Property managers who oversee multiple buildings, or automation engineers building custom scripts will find this invaluable.
Monitoring sensor readings across different units to quickly identify maintenance issues or verify security states.
Testing and calling specific Home Assistant services (like script.turn_on) in a development workflow without needing the UI.
Building complex, multi-step routines that involve checking sensor data before activating lights or media players.
Benefits of connecting Home Assistant MCP
Instant device status checks. Instead of navigating through multiple apps, you simply ask the agent to check a specific sensor's state using get_entity_state, and it tells you the number right away.
Comprehensive control over all devices. You can adjust lights, set temperatures via call_ha_service, or even manage media playback—all through natural conversation without writing code.
Deep operational visibility. Use list_entity_states to see every single device connected to your network at a glance, making it easy to find the exact ID you need for advanced scripting.
Troubleshooting and auditing. When things go wrong, check historical data using get_entity_history or review system activity with get_logbook_entries to pinpoint exactly when an issue started.
Advanced automation building. You can simulate triggers by running a custom event via fire_ha_event, allowing you to test your entire home's logic flow before deploying changes.
Home Assistant MCP use cases
Checking security status after a power outage
A property manager asks their agent, 'What is the current state of all door and window sensors?' The agent uses list_entity_states to report back whether every access point was properly secured or if any were left open.
Setting up a movie night routine
A user prompts, 'Start Movie Night.' The agent executes multiple commands using call_ha_service: it dims the lights, lowers the motorized blinds (cover), and turns on the media player.
Investigating a temperature fluctuation
An automation engineer asks the agent to check climate data. The agent uses get_entity_history on the thermostat entity to show a graph of how the temperature drifted over the last six hours, identifying when the HVAC system failed.
Running complex scripts for testing
A developer wants to test a new automation sequence. Instead of triggering it manually, they use fire_ha_event with a custom event type, ensuring their workflow logic works correctly without physical intervention.
Home Assistant MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Copying API calls directly
The user tries to manually construct the JSON payload for every single service call (e.g., writing out domain: light, service: turn_on...) and pastes it into their agent prompt.
Just tell your agent what you want in plain English: 'Turn on the kitchen lights.' The agent handles generating the correct parameters and calling the appropriate function (call_ha_service).
Focusing only on current state
The user asks, 'Is the living room light on?' but doesn't know if it was ever off before or what its history is.
To get a complete picture, first use get_entity_state for the immediate status. Then, run get_entity_history to analyze state changes over time.
Overlooking available actions
The user only knows how to toggle a switch and doesn't realize they can set specific brightness or color temperatures.
Always run list_available_services first. This shows you every possible action, like setting color temperature for lights or changing HVAC modes.
When to use Home Assistant MCP
Use this MCP if your primary need is translating natural language into physical actions within a controlled environment, such as a smart home or industrial building. If your task involves reading data from diverse sources—like combining sensor readings with calendar events—this MCP provides the necessary state management tools (get_entity_state, list_available_services). Don't use this if you just need to manage cloud-based SaaS records (use a database connector) or if your devices communicate via protocols other than Home Assistant. If you are only building simple, standalone scripts that don't require state monitoring, writing direct API calls might be faster; however, for robust agentic workflows, the conversational approach here is unmatched.
Frequently asked questions about Home Assistant MCP
How do I check if this Home Assistant MCP works with my local network? +
Yes, it supports both Nabu Casa cloud and local instances. You simply provide the correct URL format when configuring your agent's connection details.
Can I use the get_entity_state tool to see all my devices? +
You can list everything using list_entity_states. This function returns a comprehensive list of every entity ID, its current status, and key attributes.
What is the best way to control lights with Home Assistant MCP? +
Use the call_ha_service tool. You specify the domain (like 'light') and the service name (like 'turn_on'), along with any necessary parameters like brightness or color.
Does this MCP help me troubleshoot my automations? +
Absolutely. By using get_logbook_entries and checking entity history via get_entity_history, you can trace back exactly when a state changed and why, solving tough automation puzzles.
Do I need to know coding if I use the Home Assistant MCP? +
No. You don't write code; your agent does. You just talk naturally to it, letting it handle the API calls using tools like call_ha_service in the background.
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.