Slhad Aha Mcp

ai.smithery由 smithery.ai 发布官方发布者v0.1.0更新于 Nov 10, 2026

A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…

发布方自己的服务：222wcnm Bilistalkermcp

已验证Streamable HTTP可网页运行位置与生活效率与工作流

概览

AI 生成的概览

让助手查询和控制 Home Assistant 实体、调用服务，并管理自动化、仪表板与配置。

可以做什么
这是一个 TypeScript 编写的 MCP 服务器，在 Home Assistant 与 MCP 客户端之间架起桥梁（R5）。它可以列出和搜索实体、读取和更新实体状态，并调用 Home Assistant 服务，例如开关设备（R7-R9、R14）。它还支持自动化管理（列出、创建、更新、删除、追踪、校验）、访问实体与设备注册表、更新 Lovelace 仪表板、校验配置，以及协助集成配置流程（R10-R13、R39-R44）。支持 stdio、SSE 和 Streamable HTTP 三种传输方式（R17-R19）。
适用场景
当你希望用自然语言让助手查看或操作 Home Assistant 时适用：检查传感器和开关状态、开关设备，或起草并校验自动化与仪表板。适合已经运行 Home Assistant、并希望从 MCP 客户端以工具方式访问的用户。若没有可连接的 Home Assistant 实例，则用处不大。
运行要求
需要一个可访问的 Home Assistant 实例地址（HASS_URL）以及长期访问令牌（HASS_ACCESS_TOKEN），缺少令牌服务器无法启动（R95、R96）。本地运行需 Node.js v18 或更高版本，也可用 Docker/Podman 容器部署（R109、R110）。可选变量：DEBUG、RESOURCES_TO_TOOLS、LIMIT_RESOURCES（R97-R105）。远程 Smithery 端点需要 Authorization bearer 令牌请求头（V1.1）。
安装前请注意
该服务器需要 Home Assistant 长期访问令牌（HASS_ACCESS_TOKEN），该令牌可广泛控制实例，应视为敏感密钥。相关工具可更改状态、调用服务，并创建、更新或删除自动化与仪表板（R8、R9、R10、R39），可能产生非预期写入。工具定义会占用 LLM 上下文 token，部分工具单个就消耗数千 token（R46、R47）。README 说明文档主要由 AI 生成（R27）。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Slhad Aha Mcp，将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.smithery%2Fslhad-aha-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "slhad-aha": {
      "type": "http",
      "url": "https://server.smithery.ai/@slhad/aha-mcp/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

AHA Model Context Protocol (MCP) Server

Quick install links

STDIO

[Install in VS Code]

[Install MCP Server]

Others
[smithery badge]

Pretty useful to test it without IDE

AHA stands for Another Home Assistant MCP Server

This repository implements a Model Context Protocol (MCP) server for Home Assistant, providing a bridge between Home Assistant and MCP clients.

With this server, you can:

  • List and query Home Assistant entities (lights, sensors, switches, etc.)
  • Retrieve and update the state of entities
  • Call Home Assistant services (e.g., turn on/off devices)
  • Manage automations: list, create, update, and validate automations
  • Access and update the entity registry
  • Integrate and update Lovelace dashboards
  • Validate Home Assistant configuration
  • Search for entities by prefix or regex
  • Access entity sources and registry information

The server supports multiple transport methods:

  • STDIO: Traditional MCP client communication (default)
  • Server-Sent Events (SSE): Web-based real-time communication
  • Streamable HTTP: HTTP-based MCP communication for web integration

Table of Contents

Motivation

While exploring existing MCP server implementations for Home Assistant, I found that:

  • Many repositories did not provide a buildable or working Docker image, making deployment difficult or impossible.
  • Several projects did not actually implement the features or protocol described in their own README files.
  • Some solutions were outdated, unmaintained, or lacked clear documentation and test coverage.

This project aims to address these gaps by providing a reliable and fully functional MCP server with straightforward Docker support and a focus on real-world usability.

Special Mention: Most of the documentation in this project is generated or assisted by AI. As this is a side project (even though I work as a developer), I focus on building fun and working features, and prefer to review and accept generated documentation if it's good enough, rather than writing everything by hand.

Features

  • Home Assistant client integration
  • Entity registry and management
  • Automation and configuration MCP endpoints
  • Lovelace dashboard support
  • Multiple transport options: stdio, Server-Sent Events (SSE), and Streamable HTTP
  • TypeScript codebase with Vitest for testing
  • Docker support for easy deployment

Available Tools

This MCP server provides comprehensive tools for interacting with Home Assistant, including:

  • Automation Management: Create, update, delete, and trace automations
  • Entity Operations: Query and manipulate Home Assistant entities
  • Service Calls: Execute Home Assistant services
  • Configuration: Validate and manage Home Assistant configuration
  • Registry Access: Access entity and device registries
  • Config Entry Flow Helpers: Create and manage Home Assistant integration flows

⚠️ TOKEN COST WARNING

Important: Each tool definition consumes tokens in your LLM context, even if unused! Some tools (like update-lovelace-config) can cost 4,000+ tokens alone. Consider excluding unnecessary tools to minimize token consumption and maximize conversation efficiency.

For a complete list of all available tools with detailed descriptions and parameters, see the Tools Documentation.

Generating Tools Documentation

The tools documentation is automatically generated from the MCP server:

sh
npm run generate-docs

This command will:

  1. Extract all available tools from the MCP server using the inspector
  2. Generate a comprehensive markdown documentation file (tools.md)
  3. Clean up temporary files

Note: The tools documentation shows the server currently provides 39 tools for comprehensive Home Assistant integration.

Project Structure

  • src/ - Main source code
    • hass/ - Home Assistant client and helpers
    • server/ - MCP server implementations
    • mcpTransports.ts - Transport layer implementations (HTTP, SSE)
  • tests/ - Test files and Home Assistant config examples
  • scripts/ - Build and documentation generation scripts
  • Dockerfile - Containerization support
  • package.json - Project dependencies and scripts
  • tsconfig.json - TypeScript configuration
  • vitest.config.ts - Vitest test runner configuration

Example: Running the MCP Server

The MCP server supports multiple transport methods. You can run it using the same command and argument structure as in your mcp_settings.json.

1. Run with STDIO Transport (Default)

For traditional MCP client integration via stdio (server is launched by MCP client):

jsonc
{  "type": "stdio",  "command": "tsx",  "args": [    "c:/dev/git/aha-mcp/src/index.ts"  ],  "env": {    "LIMIT_RESOURCES": "-1",    "RESOURCES_TO_TOOLS": "true",    "DEBUG": "true",    "HASS_URL": "https://your-home-assistant.local:8123",    "HASS_ACCESS_TOKEN": "<your_token_here>"  }}

2. Run with Server-Sent Events (SSE) Transport

For SSE-based MCP communication, you need to run the server separately and then configure the MCP client to connect via URL.

Step 1: Start the SSE server

bash
# Start the server with SSE transport using npm scriptHASS_URL=https://your-home-assistant.local:8123 HASS_ACCESS_TOKEN=<your_token_here> npm run start:local:sse
# Or with additional configurationRESOURCES_TO_TOOLS=true DEBUG=true HASS_URL=https://your-home-assistant.local:8123 HASS_ACCESS_TOKEN=<your_token_here> npm run start:local:sse

Step 2: Configure MCP client to connect via URL

jsonc
{  "url": "http://localhost:8081/sse",  "alwaysAllow": [    // your allowed tools here  ]}

3. Run with Streamable HTTP Transport

For HTTP-based MCP communication, you need to run the server separately and then configure the MCP client to connect via URL.

Step 1: Start the HTTP server

bash
# Start the server with streamable HTTP transport using npm scriptHASS_URL=https://your-home-assistant.local:8123 HASS_ACCESS_TOKEN=<your_token_here> npm run start:local:http

Step 2: Configure MCP client to connect via URL

jsonc
{  "url": "http://localhost:8081/mcp",  "alwaysAllow": [    // your allowed tools here  ]}

4. Quick SSE Server Startup

Start the SSE server directly with npm scripts:

bash
# Set your Home Assistant credentials firstexport HASS_URL=https://your-home-assistant.local:8123export HASS_ACCESS_TOKEN=<your_token_here>
# Start SSE server with RESOURCES_TO_TOOLS enabledRESOURCES_TO_TOOLS=true DEBUG=true npm run start:local:sse

Then configure your MCP client with:

jsonc
{  "url": "http://localhost:3000/sse"}

5. Run with Podman/Docker - STDIO Transport

For STDIO transport with containers:

jsonc
{  "type": "stdio",  "command": "podman",  "args": [    "run",    "-i",    "--rm",    "-e",    "HASS_URL=https://your-home-assistant.local:8123",    "-e",    "HASS_ACCESS_TOKEN=<your_token_here>",    "ghcr.io/slhad/aha-mcp:latest"  ]}

6. Run with Podman/Docker - HTTP/SSE Server

For HTTP/SSE transports, run the server separately in a container:

Step 1: Start the server container

bash
# For SSE transportpodman run -p 8081:8081 -e HASS_URL=https://your-home-assistant.local:8123 -e HASS_ACCESS_TOKEN=<your_token_here> ghcr.io/slhad/aha-mcp -- sse
# For HTTP transport  podman run -p 8081:8081 -e HASS_URL=https://your-home-assistant.local:8123 -e HASS_ACCESS_TOKEN=<your_token_here> ghcr.io/slhad/aha-mcp -- http

Step 2: Configure MCP client

jsonc
{  "url": "http://localhost:3000/sse",  // for SSE  // or  "url": "http://localhost:3000/mcp"   // for HTTP}

Replace <your_token_here> with your actual Home Assistant access token.

Environment Variables

The following environment variables can be set to configure the MCP server:

  • HASS_URL (required): The URL of your Home Assistant instance. Example: https://your-home-assistant.local:8123 (default in code: http://localhost:8123)
  • HASS_ACCESS_TOKEN (required): Long-lived access token for Home Assistant. The server will not start without this.
  • DEBUG: Set to true to enable debug logging. Default: false.
  • RESOURCES_TO_TOOLS: Set to true to enable mapping resources to tools. Default: false.
    • Detailed explanation: When enabled, this option exposes Home Assistant resources (such as entities, automations, and services) as individual tools for MCP clients. This is especially useful for clients or agents that can only interact with the server via tool-based interfaces, rather than through generic resource queries. It allows such clients to discover and use Home Assistant features as discrete, callable tools, improving compatibility and usability for tool-limited environments.
  • LIMIT_RESOURCES: Set to a number to limit the number of resources returned by the server. Default: unlimited.

Note: The server transport method is now controlled by command line arguments (sse or http) rather than environment variables.

Getting Started

Prerequisites

  • Node.js (v18+ recommended)
  • Docker (optional, for containerized deployment)

Installation

sh
npm install

Running the Server

For STDIO transport (launched by MCP client):

sh
# Set environment variables and run with npmnpm start

For HTTP/SSE transports (run server separately):

sh
# Run SSE server on port 8081npm run start:local:sse
# Run HTTP server on port 8081:8081npm run start:local:http
# Quick SSE server startup with environment variablesRESOURCES_TO_TOOLS=true DEBUG=true npm run start:local:sse

Then configure your MCP client to connect via URL:

  • SSE: "url": "http://localhost:3000/sse"
  • HTTP: "url": "http://localhost:8080/mcp"

Running Tests

sh
npm run test:short

Note: The unit tests currently run against a real Home Assistant instance and are not mocked yet. This means tests require a live Home Assistant server and valid credentials to execute successfully.

Docker Usage

Build and run the server in a Docker container:

sh
# Build the containernpm run docker

then follow :

For HTTP/SSE modes, then configure your MCP client with the appropriate URL:

  • SSE: "url": "http://localhost:3000/sse"
  • HTTP: "url": "http://localhost:8081/mcp"

Contributing

Pull requests are welcome! For major changes, please open an issue first to discuss what you would like to change.

License

See LICENSE for details.

来源：README.md，提交 a212cba

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Smithery 集成

222wcnm Bilistalkermcp

ai.smithery官方发布者

Bilibili 创作者分析服务器，让助手查询指定用户的资料、视频、动态、专栏、字幕、关注列表和评论。

Streamable HTTP可网页运行
知识与记忆尚未收录Oct 24, 2026

Zwldarren Akshare One Mcp

ai.smithery官方发布者

远程 MCP 服务器，让助手以只读方式获取中国股市数据：历史与实时行情、新闻和财务报表。

Streamable HTTP可网页运行鉴权
金融需要凭据Oct 24, 2026

Zhaoganghao Hellomcp

ai.smithery官方发布者

一个小型远程 MCP 服务器，让助手按名字向人问候，并介绍“Hello, World”的由来。

Streamable HTTP可网页运行
尚未收录Oct 24, 2026

Zeta Chain Cli

ai.smithery官方发布者

一个远程 MCP 服务器，让助手为任意姓名或受众生成友好、可定制的问候语。

Streamable HTTP可网页运行鉴权
需要凭据Oct 24, 2026

Yuna0x0 Hackmd Mcp

ai.smithery官方发布者

一个连接 HackMD API 的 MCP 服务器，让助手读取、创建、更新和删除 HackMD 笔记并管理团队。

Streamable HTTP可网页运行
沟通与协作尚未收录Oct 25, 2026