Enables natural language interaction with Home Assistant entities using the Model Context Protocol.
Enables natural language interaction with Home Assistant entities using the Model Context Protocol.
Create a .env file in your current directory with the following variables:
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| states | Query entity states |
| lights | List lights |
| light | Control a light |
| service | Call Home Assistant services |
| history | Retrieve historical entity data |
| services | List available services |
| config | Get Home Assistant configuration |
| domains | List available domains |
| error_log | Get Home Assistant error log |
| devices | Get all devices in Home Assistant |
| Variable | Description | Required |
|---|---|---|
| HASS_URL | Endpoint or connection string the server talks to. | Yes |
| HASS_TOKEN | Credential the server authenticates with. | Yes |
| HASS_MOCK | Configuration value read at startup. | Optional |
Integrates with Home Assistant to provide smart home control capabilities via Model Context Protocol (MCP).
A Model Context Protocol (MCP) server that enables AI agents to interact with the 1NCE IoT connectivity management platform through natural language.
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
Before using the EMQX MCP Server tools, you need to set up an EMQX cluster with properly configured API Key and client authentication. There are
Evidence-based humanoid robot data: RadarScore ratings, evidence grades A-D, prices, EU availability
The binary will be installed to your GOBIN directory, which should be in your PATH.