What are the runtime dependencies?
Node.js and npm are required to build and run the server. A running Home Assistant instance with a long-lived access token is also needed.
@hekmon8
Basic information
A Model Context Protocol (MCP) server for interacting with Home Assistant. This server provides tools to control and monitor your Home Assistant devices through MCP-enabled applications.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"Homeassistant-server-mcp": {
"command": "npx",
"args": [
"-y",
"@smithery/cli",
"install",
"@hekmon8/Homeassistant-server-mcp",
"--client",
"claude"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
This is a Model Context Protocol (MCP) server for interacting with Home Assistant. It provides tools to control and monitor Home Assistant devices through MCP-enabled applications, such as Claude Desktop. It is designed for Home Assistant users who want to integrate AI assistants with their smart home setup.
Install automatically via Smithery (npx -y @smithery/cli install @hekmon8/Homeassistant-server-mcp --client claude) or manually by cloning the repo, running npm install and npm run build, then configuring the MCP settings file with your Home Assistant URL (HA_URL) and a long-lived access token (HA_TOKEN). The server exposes four tools: get_state, toggle_entity, trigger_automation, and list_entities.
Node.js and npm are required to build and run the server. A running Home Assistant instance with a long-lived access token is also needed.
Set the `HA_URL` and `HA_TOKEN` environment variables in your MCP settings file. Always use HTTPS for your Home Assistant instance, keep access tokens secret, and never commit them to version control.
All device data stays on your local Home Assistant instance. The MCP server only reads from and writes to your instance; no data is sent to external services.
The server uses the standard Model Context Protocol (MCP) for communication with MCP-enabled clients.
Fork the repository and submit pull requests. For issues, check existing repository issues or create a new one with context. Additional support resources are available at www.aimcp.info.

ATL doesn’t just help agents find tools — it gets the job done. It finds and chooses the right AI provider, tool, or MCP server, executes the task, and switches to a fallback when a provider fails. It can optimize for lo

Search a registry of agent skills and MCP servers, run them for real (sandbox or remote MCP, no install, a trace on every run), and hire proven agents for USDC.

Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a recei
Model Context Protocol (MCP) server for Hostinger API. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: This opens a browser window to authorize via OAuth. Once app

Tokenaissance is a online Personal Agent for Quant and Research investment available at https://tokenaissance.com.
Comments