Home Assistant MCP server
Home Assistant runs the smart home of many people who host it themselves. Through Flowplane an AI assistant can list your devices and sensors with their state, read one device’s details, look at how a sensor changed over time and read the logbook. It can call any Home Assistant service, such as turning on a light or setting the thermostat, and each call waits for your approval first.
- Tools
- 5 read · 1 change
- Sign-in
- Own account or shared key
- Approval, by default
- Changes wait for you
- MCP server
- Flowplane’s tools
What your assistant can do in Home Assistant
5 tools that read and 1 that change something in Home Assistant. Reads are allowed; a change marked “asks first” waits for the person’s approval by default, and your workspace’s rules decide the rest.
Reads5
- List devices and sensorsEntities and their states, by kind or by name
list_entities - Read a device's stateIts state and details
get_entity - Read a device's historyHow its state changed over time
get_history - Read what happenedThe logbook: what changed and when
get_logbook - List the actionsWhat can be switched or started, by kind
list_services
Changesasks first1
- Control a deviceAny Home Assistant service, asked first
call_service
Sign-in
There are two ways in. With an access token (recommended), you paste your Home Assistant’s address and a long-lived access token made under your profile, Security; the token acts with the rights of the user who made it. With Sign in, you give the address and sign in on Home Assistant’s own page with an administrator account. Either way Flowplane keeps the credentials sealed; the assistant never sees them.
In Flowplane: In the Flowplane console, add Home Assistant, choose Access token or Sign in, and give the address where you open Home Assistant. An address inside your home network works through a tunnel, with an access token.
Home Assistant and MCP
Home Assistant has an official MCP server of its own: the Model Context Protocol Server integration, which you add in Home Assistant. Flowplane offers both: the Access token way, with Flowplane’s own tools on Home Assistant’s REST API, the same in every version; and the Sign in way, which passes Home Assistant’s MCP server through, with the tools Assist exposes.
Things to ask
- “Which lights are still on?”
- “What was the temperature in the living room overnight?”
- “Did the front door open while we were away this weekend?”
- “Set the thermostat to 20 degrees.”
- “Turn on the kitchen lights at 40% brightness.”
Connect your assistant to Home Assistant
One Flowplane address works in every assistant below, with the same rules and the same log. Step-by-step setup for each:
- Connect Claude to Home AssistantClaude on the web and in the desktop app→
- Connect Claude Code to Home AssistantAnthropic’s coding agent in the terminal→
- Connect ChatGPT to Home AssistantChatGPT on the web→
- Connect Cursor to Home AssistantThe Cursor code editor→
- Connect Codex to Home AssistantOpenAI’s coding agent, in the terminal and the IDE→
- Connect GitHub Copilot to Home AssistantCopilot Chat in VS Code, in agent mode→
- Connect Mistral Le Chat to Home AssistantMistral’s assistant (Le Chat, now called Vibe)→
Questions
- Which way should I choose, Access token or Sign in?
- Access token is recommended: it works with any Home Assistant version, also inside your home network through a tunnel, and its tools are Flowplane’s, so they do not depend on what Assist exposes. Sign in needs a recent Home Assistant with the Model Context Protocol Server integration, reachable from the internet with its External URL set, and an administrator account.
- Can the assistant unlock my door?
- It can ask to. Control a device can call any Home Assistant service, locks, alarms and garage doors included, and it asks a person to approve every call by default. If an admin sets it to allow, assistants can do anything Home Assistant can, with the rights of the token’s user, so keep it on ask. Through Sign in, Assist’s tools count as changes and ask too.
- What is left out on purpose?
- With the access token: rendering templates (they run code on your Home Assistant), configuration, firing events, the error log and camera images. History and the logbook are read in windows of at most 7 days. Home Assistant’s REST API does not know areas, so devices are found by kind and by words in their name, such as the room.
- Which AI assistants can use Home Assistant through Flowplane?
- Claude, Claude Code, ChatGPT, Cursor, Codex, GitHub Copilot and Mistral Le Chat, and any other client that supports remote MCP servers with sign-in. They all reach Home Assistant through the same Flowplane address.
- What does it cost?
- Free for one person, with up to three apps and five assistants. Personal Pro is €9 a month including VAT; companies start at €99 a month for ten active users. Prices are indicative; see the pricing page.
Flowplane is not affiliated with or endorsed by Home Assistant’s maker; the name and logo only identify the app. Pricing
Let your AI work with your data. Safely, from today.
Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.