
Mcp Homeassistant
io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Oct 24, 2026
MCP server exposing Home Assistant REST API functionality
Overview
A local MCP server that connects an assistant to a Home Assistant instance's REST API to inspect and control smart-home entities, services, events and calendars
- What you can do
- Check API status, configuration, loaded components, event types and available services by domain, and read all entity states or a single entity's state, plus current config, states, services and components as resources. Create, update or delete entity states, fire custom events and call Home Assistant services. Render Jinja templates and handle intents. Retrieve historical state changes, logbook entries, the error log and calendar entities and events. Validate the configuration file.
- When to use it
- Useful when you want an assistant to query or control a Home Assistant smart-home setup from the desktop, for example reading sensor states, reviewing history and logs, or triggering services and events.
- Requirements
- Runs as a local Python process installed from PyPI (pip install mcp-homeassistant). Needs a reachable Home Assistant URL via the HA_URL environment variable (default and a Long-Lived Access Token in HA_TOKEN, which is required. Network access to the Home Assistant instance.
Installation
In SourceWeft
- Open Mcp Homeassistant in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-homeassistant
MCP server exposing Home Assistant 2026.4.1 REST API functionality.
mcp-name: io.github.daedalus/mcp-homeassistant
Install
Configuration
Set the following environment variables:
HA_URL: Home Assistant URL (default: http://localhost:8123)HA_TOKEN: Long-Lived Access Token (required)
Usage
Tools
The MCP server exposes the following tools:
get_api_status- Check if the API is runningget_config- Get HA configurationget_components- List loaded componentsget_events- List event types and listener countsget_services- List available services by domainget_states- Get all entity statesget_state- Get a specific entity stateset_state- Update or create an entity statedelete_state- Delete an entity statefire_event- Fire a custom eventcall_service- Call a Home Assistant servicerender_template- Render a Jinja templateget_history- Get historical state changesget_logbook- Get logbook entriescheck_config- Validate configuration.yamlhandle_intent- Handle an intentget_error_log- Get error logget_calendars- List calendar entitiesget_calendar_events- Get calendar events
Resources
homeassistant://config- Current confighomeassistant://states- All entity stateshomeassistant://services- Available serviceshomeassistant://components- Loaded components
Development
Source: README.md at commit 330dcaf
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts