🏠 Home Assistant MCP Server

🚀 Control your smart home through AI assistants in seconds. Manage lights, switches, sensors, climate, and media players. No coding, no custom server setup required.

🕒 Last updated: 2026-04-16 · 🛠️ 5 tools · 📚 2 resources · 🔌 Full MCP Protocol support · 💰 Pay Per Event pricing

Home Assistant is the most popular open-source home automation platform, connecting hundreds of smart device brands into one unified system. This MCP (Model Context Protocol) server lets AI assistants interact with your Home Assistant instance directly. It provides 5 tools (get_states, get_state, call_service, get_entities, get_services) and 2 resources (entities list, services list) so your AI can read sensor data, toggle lights, adjust thermostats, play media, and call any Home Assistant service.

The server runs in standby mode on Apify's infrastructure, meaning it stays active and responds instantly to requests. You provide your Home Assistant URL and a long-lived access token in each request body. There is no startup delay, no Docker containers to manage, and no port forwarding required. Just connect your AI assistant to this MCP endpoint and start controlling your smart home with natural language commands.

🎯 Target Audience	💡 Use Cases
Smart home enthusiasts	Control devices through AI chat interfaces
Home automation developers	Build AI-driven automation workflows
IoT researchers	Prototype voice and text-based device control
Accessibility advocates	Enable hands-free home control via AI
System integrators	Connect Home Assistant to AI-driven dashboards
Tech hobbyists	Experiment with MCP protocol and smart devices

---

📋 What the Home Assistant MCP Server does

• 🔌 Get all entity states to see every device, sensor, and switch in your Home Assistant
• 🎯 Get specific entity state to check the current value of any sensor, light, or switch
• 🛠️ Call any service to toggle lights, set temperatures, play media, or trigger automations
• 📋 List all entities to discover available devices and their entity IDs
• 📚 List all services to see every action your Home Assistant supports
• 💰 Pay Per Event pricing so you only pay for the requests you make

The MCP server acts as a bridge between AI assistants and your Home Assistant instance. When your AI needs to check a temperature sensor, it calls the get_state tool with the entity ID. When it needs to turn on a light, it calls call_service with the appropriate domain, service, and entity. The server forwards these requests to your Home Assistant's REST API and returns the results to the AI.

💡 Why it matters: Without an MCP server, connecting an AI assistant to Home Assistant requires custom code, API wrappers, and server management. This actor handles all of that, giving your AI direct access to your smart home through a standard protocol.

---

🎬 Full Demo

🚧 Coming soon...

---

⚙️ Input

Field	Type	Required	Description
This actor runs in standby mode. No input is required at startup. Credentials are provided in each request body.

Each request body must include:

Field	Type	Required	Description
homeAssistantUrl	string	Yes	URL of your Home Assistant instance (e.g., https://homeassistant.local:8123)
homeAssistantApiKey	string	Yes	Long-lived access token from Home Assistant

Example 1: Get all entity states

{
  "tool": "get_states",
  "homeAssistantUrl": "https://homeassistant.local:8123",
  "homeAssistantApiKey": "your_long_lived_access_token"
}

Example 2: Call a service to toggle a light

{
  "tool": "call_service",
  "domain": "light",
  "service": "toggle",
  "entity_id": "light.living_room",
  "homeAssistantUrl": "https://homeassistant.local:8123",
  "homeAssistantApiKey": "your_long_lived_access_token"
}

⚠️ Good to Know: You need a running Home Assistant instance and a long-lived access token. Create the token at Profile > Long-Lived Access Tokens in your Home Assistant dashboard. Your Home Assistant must be accessible from the internet (or use a tunnel like Nabu Casa).

---

📊 Output

🧾 Schema

Emoji	Field	Type	Description
🆔	entity_id	string	Unique identifier for the device or sensor
📊	state	string	Current state value (on, off, temperature, etc.)
🏷️	attributes	object	Device attributes (brightness, color, unit, etc.)
📅	last_changed	string	When the state last changed
📅	last_updated	string	When the state was last refreshed
🔧	domain	string	Entity domain (light, switch, sensor, etc.)
📋	friendly_name	string	Human-readable device name
⚠️	error	string	Error message if the request failed

📦 Sample records

---

✨ Why choose this Actor

Feature	Details
🔌 Full MCP support	Standard Model Context Protocol for AI assistant integration
🛠️ 5 tools	Get states, get state, call service, list entities, list services
📚 2 resources	Entities list and services list for discovery
⚡ Standby mode	Always running, instant response with no cold start
🏠 Any device	Works with any device integrated into Home Assistant
💰 Pay Per Event	Only pay for the requests you actually make
🔒 Secure	Credentials sent per-request, never stored

📊 Control any of the 2,000+ device integrations supported by Home Assistant through a single MCP endpoint.

---

📈 How it compares to alternatives

Feature	This Actor	Self-Hosted MCP	Custom API Wrapper
No server management	✅	❌	❌
Standard MCP protocol	✅	✅	❌
Instant response (standby)	✅	Depends	Depends
Pay Per Event pricing	✅	❌	❌
Works with any AI assistant	✅	✅	Custom
No coding required	✅	❌	❌
Automatic scaling	✅	❌	❌

Connect your AI to Home Assistant in minutes instead of building and maintaining custom infrastructure.

---

🚀 How to use

1. Create an Apify account - Sign up free with $5 credit
2. Set up Home Assistant - Install Home Assistant and integrate your smart devices
3. Create an access token - Go to Profile > Long-Lived Access Tokens in Home Assistant
4. Start the MCP Server - Launch the actor in standby mode on Apify
5. Connect your AI assistant - Point your MCP-compatible AI to the actor's endpoint with your credentials

⏱️ Setup takes under 5 minutes. The server stays running and responds to requests instantly.

---

💼 Business use cases

🏠 Smart Home Control Toggle lights and switches through AI chat Check sensor readings with natural language Adjust thermostats and climate controls remotely Trigger automation scenes via AI commands	🔧 Development & Prototyping Build AI-driven home automation prototypes Test MCP protocol integrations with real devices Develop custom AI assistants for smart buildings Create voice-controlled device management systems
♿ Accessibility Enable hands-free home control for mobility-limited users Create text-based interfaces for hearing-impaired users Build simplified AI interfaces for elderly care Automate routine tasks with conversational triggers	📊 Monitoring & Analytics Collect sensor data for energy usage analysis Monitor home security sensors through AI dashboards Track environmental conditions across rooms Build reporting systems from device state data

---

🔌 Automating Home Assistant MCP Server

Integrate the Home Assistant MCP Server into your workflow using the Apify API or client libraries.

Node.js:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor("parseforge/home-assistant-mcp-server").call({});
// The actor runs in standby mode - connect to it via the MCP endpoint
console.log("MCP server running at:", run.defaultKeyValueStoreId);

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("parseforge/home-assistant-mcp-server").call(run_input={})
# The actor runs in standby mode - connect to it via the MCP endpoint
print("MCP server running")

• 📖 Apify API reference
• 🐍 Python client docs
• 📦 Node.js client docs

Schedules: The MCP server runs in standby mode, so it stays active continuously. No scheduling is needed. It responds to requests as they come in, with no cold start delay.

---

❓ Frequently Asked Questions

---

🔌 Integrate with any app

• 🔗 Make (Integromat) - Connect Home Assistant events to 1,500+ apps and services
• 🔗 Zapier - Trigger workflows based on Home Assistant state changes
• 🔗 Slack - Get notified about smart home events in your channel
• 🔗 Airbyte - Stream sensor data into your data warehouse for analytics
• 🔗 GitHub - Store device configuration and automation scripts
• 🔗 Google Drive - Log sensor readings to spreadsheets automatically

---

🔗 Recommended Actors

Actor	Description
Markdown to PDF MCP Server	Convert markdown documents to PDF through MCP protocol
HTML to JSON Smart Parser	Parse HTML content into structured JSON data
Smart Apify Actor Scraper	Discover and analyze Apify actors with quality metrics
Lead Formatter Tool	Format and enrich lead data for CRM systems
MultiSite URL Shortener	Generate shortened URLs across multiple services

💡 Pro Tip: Combine the Home Assistant MCP Server with Make or Zapier to create automated workflows that respond to smart home events with external actions.

---

🆘 Need Help? Open our contact form and we will get back to you within 24 hours. We are happy to help with custom setups, integrations, or feature requests.

---

Disclaimer: This actor is not affiliated with, endorsed by, or connected to Home Assistant or Nabu Casa. It integrates with Home Assistant through its published REST API. Use responsibly and in accordance with applicable terms of service.