MCP.Market

Homeassistant MCP server

by daedalus·io.github.daedalus/mcp-homeassistant·v0.1.0
No reviews yet

MCP server exposing Home Assistant REST API functionality

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed Homeassistant yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Homeassistant tools (19, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • call_service

    Call a service within a specific domain.

  • check_config

    Validate configuration.yaml.

  • delete_statewrite action

    Delete an entity state.

  • fire_event

    Fire a custom event in Home Assistant.

  • get_api_status

    Check if the Home Assistant API is running.

  • get_calendar_events

    Get events from a specific calendar.

  • get_calendars

    Get list of calendar entities.

  • get_components

    Get list of currently loaded components.

  • get_config

    Get the current Home Assistant configuration.

  • get_error_log

    Get the error log from the current session.

  • get_events

    Get list of event types and their listener counts.

  • get_history

    Get historical state changes for entities.

  • get_logbook

    Get logbook entries.

  • get_services

    Get list of available services organized by domain.

  • get_state

    Get the state of a specific entity.

  • get_states

    Get all entity states in Home Assistant.

  • handle_intent

    Handle an intent.

  • render_template

    Render a Home Assistant template.

  • set_statewrite action

    Update or create the state of an entity.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 159 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Homeassistant compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,273 servers
Tools
19
the typical server has 7
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
28
more than 16% of 11,915 servers with a package

What its tools let an agent do: 17 read · 1 change · 1 delete

Install Homeassistant in Claude Code, Cursor or VS Code

claude mcp add mcp-homeassistant -- uvx mcp-homeassistant
Add to Cursor

What the publisher says

From the Homeassistant repository's README, as published. We do not edit it. Read it on GitHub

mcp-homeassistant

MCP server exposing Home Assistant 2026.4.1 REST API functionality.

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

Install

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

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

Tools

The MCP server exposes the following tools:

  • getapistatus - 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

Resources

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

Development

git clone https://github.com/daedalus/mcp-homeassistant.git
cd mcp-homeassistant
pip install -e ".[test]"

# run tests
pytest

# format
ruff format src/ tests/

# lint
ruff check src/ tests/

# type check
mypy src/

Nothing above is checked by us. What we check is on the safety report.

Homeassistant: common questions

Is Homeassistant MCP server safe?
Mostly: it is graded B (82/100). Read the Homeassistant safety report
How do I install Homeassistant?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Homeassistant need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Homeassistant maintained?
The last commit was 195 days ago (2026-04-21). The latest release is v0.1.0.
How does Homeassistant compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,273 servers); tools 19 (the typical server has 7); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from daedalus →