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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago