Home Assistant Model Context Protocol (MCP)

Created By
jango-blockchaineda year ago
An advanced MCP server for Home Assistant. 🔋 Batteries included.
Overview

What is MCP Server for Home Assistant?

MCP Server is a lightweight integration tool designed for Home Assistant, providing a flexible interface for device management and automation, built for performance and ease of use.

How to use MCP Server?

To use MCP Server, clone the repository, set up the environment, configure your Home Assistant details in the .env file, and build and launch the server using Docker.

Key features of MCP Server?

  • Basic device control via REST API
  • WebSocket/Server-Sent Events (SSE) for real-time state updates
  • Simple automation rule management
  • JWT-based authentication
  • Optional speech features including wake word detection and speech-to-text capabilities

Use cases of MCP Server?

  1. Automating smart home devices through voice commands.
  2. Integrating various smart devices with Home Assistant for seamless control.
  3. Utilizing speech recognition for hands-free operation of home automation.

FAQ from MCP Server?

  • What is required to run MCP Server?

    You need the Bun runtime, a Home Assistant instance, and optionally Docker and Node.js for additional features.

  • Can I use speech features without a GPU?

    Yes, but GPU acceleration is recommended for better performance in speech processing.

  • Is MCP Server open-source?

    Yes, MCP Server is open-source and available on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jango-blockchained
Star
9
Language
TypeScript
License
Apache-2.0 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)

8 hours ago
Alloy

2 days ago