🤝

Created By
miguelg719a year ago
An MCP server for Home Assistant
Overview

what is Home Assistant MCP?

Home Assistant MCP is an integration server for Home Assistant that utilizes Model Context Protocol (MCP) to enhance smart home control capabilities through domain-specific tools.

how to use Home Assistant MCP?

To use the Home Assistant MCP server, you need to configure environment variables in a .env file with your Home Assistant token and base URL, then follow the installation guide provided in the documentation.

key features of Home Assistant MCP?

  • Control various domains within Home Assistant like lights, climate, locks, and security systems.
  • Access to a variety of tools to manage smart home devices.
  • Easy setup through environment configuration.

use cases of Home Assistant MCP?

  1. Automating the control of lights and climate settings in a smart home.
  2. Managing security systems including alarms and locks.
  3. Implementing advanced home automation through MCP integration.

FAQ from Home Assistant MCP?

  • What do I need to start using Home Assistant MCP?

You need to have Home Assistant set up with a long-lived access token and the URL of your instance.

  • Can I control multiple domains with this server?

Yes! The server supports controlling lights, climate, locks, and alarm systems.

  • Is there any development involved?

Yes! You can build and publish the MCP server using the provided development guidelines in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
miguelg719
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago