Mcp Homeassistant

io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Oct 24, 2026

MCP server exposing Home Assistant REST API functionality

Overview

AI-generated 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.
Before you install
The HA_TOKEN long-lived access token is a powerful credential granting access to the Home Assistant API; keep it secret. Several tools write or change data: set_state and delete_state modify entity states, fire_event emits events, and call_service can trigger real device actions such as locks, heating or alarms. Review actions before letting an assistant run them.

Installation

In SourceWeft

  1. Open Mcp Homeassistant in the dashboard and add it to a workspace.
  2. 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.

[PyPI] [Python] [Ruff]

mcp-name: io.github.daedalus/mcp-homeassistant

Install

bash
pip install mcp-homeassistant

Configuration

Set the following environment variables:

  • HA_URL: Home Assistant URL (default: http://localhost:8123)
  • HA_TOKEN: Long-Lived Access Token (required)

Usage

bash
export HA_URL="http://homeassistant:8123"export HA_TOKEN="your_long_lived_access_token"mcp-homeassistant

Tools

The MCP server exposes the following tools:

  • get_api_status - Check if the API is running
  • get_config - Get HA configuration
  • get_components - List loaded components
  • get_events - List event types and listener counts
  • get_services - List available services by domain
  • get_states - Get all entity states
  • get_state - Get a specific entity state
  • set_state - Update or create an entity state
  • delete_state - Delete an entity state
  • fire_event - Fire a custom event
  • call_service - Call a Home Assistant service
  • render_template - Render a Jinja template
  • get_history - Get historical state changes
  • get_logbook - Get logbook entries
  • check_config - Validate configuration.yaml
  • handle_intent - Handle an intent
  • get_error_log - Get error log
  • get_calendars - List calendar entities
  • get_calendar_events - Get calendar events

Resources

  • homeassistant://config - Current config
  • homeassistant://states - All entity states
  • homeassistant://services - Available services
  • homeassistant://components - Loaded components

Development

bash
git clone https://github.com/daedalus/mcp-homeassistant.gitcd mcp-homeassistantpip install -e ".[test]"
# run testspytest
# formatruff format src/ tests/
# lintruff check src/ tests/
# type checkmypy src/

Source: README.md at commit 330dcaf

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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