mcp-server-home-assistant

Created By
allenportera year ago
A Model Context Protocol Server for Home Assistant
Overview

what is mcp-server-home-assistant?

The mcp-server-home-assistant is a Model Context Protocol Server designed to integrate with Home Assistant to enhance home automation capabilities.

how to use mcp-server-home-assistant?

To use mcp-server-home-assistant, install the required custom component in your Home Assistant instance, create a Long Lived Access Token, and configure your local environment using the provided JSON example.

key features of mcp-server-home-assistant?

  • Integration with Home Assistant using Model Context Protocol.
  • Real-time communication via WebSocket.
  • Detailed logging for monitoring server activity.

use cases of mcp-server-home-assistant?

  1. Enabling smarter automation scenarios based on context-aware data.
  2. Interacting with Home Assistant devices using custom commands.
  3. Facilitating advanced home automation projects and setups.

FAQ from mcp-server-home-assistant?

  • What is Model Context Protocol?

Model Context Protocol is a method for creating and managing contexts in home automation systems, enhancing the communication between devices and services.

  • Do I need any special prerequisites to use this project?

Yes, you need to have Home Assistant set up and be familiar with creating and configuring custom components.

  • Is there support for troubleshooting?

Yes, you can view logs in the specified directory to troubleshoot issues with the setup.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
allenporter
Star
53
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
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.

21 hours ago