Home Assistant MCP Server
Pricing
from $15.00 / 1,000 tool executions
Home Assistant MCP Server
Runs a Model Context Protocol server that lets AI assistants control Home Assistant devices, read sensor states, and trigger automations through the REST API.
Pricing
from $15.00 / 1,000 tool executions
Rating
5.0
(2)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
0
Monthly active users
9 days ago
Last modified
Categories
Share
Home Assistant MCP Server
Connect any AI assistant to your Home Assistant smart home through a single MCP server. Control devices, query sensors, and run automations with natural language. No cloud, no extra hardware, no per-request fees.
Home Assistant stores your smart home state locally, but most AI assistants cannot reach it without custom code. This Actor exposes your Home Assistant instance as a Model Context Protocol server, so Claude, GPT, and other MCP clients can read sensors, control lights, and trigger scenes using plain English. It runs as a standby Actor on Apify and accepts your Home Assistant URL and long-lived access token in each request body.
| Who uses it | What they scrape Home Assistant for |
|---|---|
| Smart home owners | Ask a voice assistant to turn on the living room lights or check the front door sensor. |
| Home automation enthusiasts | Let an LLM write and run Home Assistant scripts without opening the dashboard. |
| AI developers | Give their MCP client direct access to a real smart home for testing and demos. |
| Accessibility users | Control lights, thermostats, and locks through a conversational interface. |
What it does
This Actor runs a Model Context Protocol server that translates MCP tool calls into Home Assistant REST API requests and returns the results as structured JSON.
- 🔌 Standby server: the Actor stays warm and waits for MCP tool calls, no input needed at startup.
- 🔐 Per-request auth: send your Home Assistant URL and long-lived access token in each request body, nothing is stored.
- 🧠 MCP native: exposes Home Assistant entities, services, and states as tools any MCP client can call.
- 📦 Structured output: every tool call returns JSON with the entity state, service result, or error message.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Home Assistant data
💡 Voice control for every room.
A smart home owner connects Claude Desktop to this Actor and says 'dim the bedroom lights to 20 percent' without opening the Home Assistant app.
📊 Sensor checks in plain English.
A homeowner asks 'is the garage door open?' and the MCP client calls the cover entity state tool, returning the current position.
🤖 LLM-driven automations.
An enthusiast lets GPT read temperature sensors and turn on a fan when the room gets too warm, all through MCP tool calls.
♿ Hands-free accessibility.
A user with limited mobility controls lights, locks, and thermostats by speaking to an assistant that calls Home Assistant services.
Why choose this scraper
| What you get | |
|---|---|
| No cloud dependency | Talks directly to your Home Assistant instance over HTTPS, your data never leaves your network. |
| Works with any MCP client | Claude Desktop, GPT, Cursor, and other Model Context Protocol hosts can connect. |
| No extra hardware | Runs on Apify infrastructure, no Raspberry Pi or always-on computer required. |
| Pay per request | Apify charges only for the compute time used by each tool call, no monthly subscription. |
How it compares
No other Store actor targets Home Assistant the same way, so the honest comparison is with the alternatives teams actually weigh.
| Home Assistant MCP Server | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Home Assistant changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
No input is required at startup. Each request body must include your Home Assistant URL and a long-lived access token, and the MCP client chooses which tools to call. The Input tab lists every parameter.
Pricing
Pay-per-result: $0.015 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $1.50 |
| 1,000 results | $15.00 |
| 10,000 results | $150.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Home Assistant MCP Server.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Home Assistant through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting a 401 Unauthorized error?
Your long-lived access token is missing, expired, or invalid. Create a new token in Home Assistant and make sure it is sent in the request body.
Why does the Actor return 'connection refused'?
Your Home Assistant URL is not reachable from Apify's servers. Make sure your instance is accessible over the public internet, or use a tunnel like Nabu Casa.
Why does my MCP client say 'tool not found'?
The MCP client may be using an outdated tool list. Reconnect the client or refresh the tool definitions from the Actor.
Why is the Actor slow to respond?
The Actor runs in standby mode and may need a cold start. Subsequent calls will be faster. If latency is high, check your Home Assistant instance's response time.
Why can't I control a specific device?
Your token may not have permission for that entity, or the entity ID is wrong. Check the entity ID in Home Assistant and ensure the token user has access.
FAQ
| Question | Answer |
|---|---|
| What is Home Assistant? | Home Assistant is an open-source home automation platform that runs locally and connects to thousands of smart home devices. It exposes a REST API for reading states and calling services. |
| What is an MCP server? | MCP stands for Model Context Protocol. An MCP server exposes tools that AI assistants like Claude or GPT can call to interact with external systems, in this case your Home Assistant instance. |
| How do I get a Home Assistant long-lived access token? | In Home Assistant, go to your profile page, scroll to Long-Lived Access Tokens, and create a token. Copy it and send it in the request body along with your Home Assistant URL. |
| Does this Actor store my Home Assistant credentials? | No. The Actor does not persist any input. Your URL and token are passed in each request body and used only for that single tool call. |
| Can I use this with Claude Desktop? | Yes. Configure Claude Desktop to connect to this Actor as an MCP server, then you can ask Claude to control your smart home. |
| What Home Assistant entities can I control? | Any entity that the Home Assistant REST API can read or control, including lights, switches, covers, climate, sensors, and scenes. |
| Does this work with Home Assistant Cloud? | Yes, as long as your Home Assistant instance is reachable over HTTPS and you have a long-lived access token, it works with local or cloud-hosted setups. |
| Is there a limit to how many devices I can control? | No hard limit. The Actor can call any service or read any entity your token has access to. |
| How much does it cost to run? | You pay only for the compute time used by each MCP tool call, based on Apify's standard pricing. There is no monthly fee. |
| Can I run this on my own server? | This Actor is designed to run on Apify. If you want to self-host, you can use the same MCP server code locally. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Home Assistant. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
