Loxone Miniserver MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
loxone-mcp
An MCP (Model Context Protocol) server that connects AI assistants to a Loxone Miniserver smart home system.
Lets Claude (or any MCP-compatible AI) list rooms, query live sensor/actuator states, search devices, and send commands.
Features
list_rooms— all rooms with their controlslist_controls— all controls (name, type, UUID, room)find_control— keyword search across name/room/typeget_status— live sensor and actuator values (optional room filter)control_device— send commands (On/Off, dimmer %, blinds, HVAC, audio)
Related MCP server: Loxone MCP Server
Requirements
Loxone Miniserver with Cloud Connect enabled
Node.js 20+ (or Docker)
Installation
npm
npm install -g @syntropic/loxone-mcpThen run with environment variables set:
LOXONE_SERIAL=XXXXXXXXXXXX \
LOXONE_USER=admin \
LOXONE_PASS=yourpass \
MCP_API_KEY=$(openssl rand -hex 32) \
loxone-mcpFrom source
git clone https://github.com/syntropicsignal-ai/loxone-mcp.git
cd loxone-mcp
cp .env.example .env
# edit .env with your Miniserver serial, credentials, and a random API key
npm install
npm run build
npm startThe server listens on http://localhost:3000. The MCP endpoint is POST /mcp.
Docker
docker build -t loxone-mcp .
docker run -p 3000:3000 --env-file .env loxone-mcpConfiguration
Variable | Required | Description |
| Yes | 12-char Miniserver serial (from Loxone Config → Miniserver) |
| Yes | Miniserver username |
| Yes | Miniserver password |
| Yes | Bearer token for MCP endpoint auth ( |
| No | HTTP port (default: 3000) |
Connecting to Claude
Add to your Claude MCP configuration:
{
"mcpServers": {
"loxone": {
"url": "https://your-server/mcp",
"headers": {
"Authorization": "Bearer YOUR_MCP_API_KEY"
}
}
}
}Supported commands by device type
Type | Commands |
Switch / Light |
|
Dimmer |
|
Jalousie (blinds) |
|
Gate |
|
HVAC ( |
|
AudioZone |
|
Architecture
Stateless HTTP server — each POST /mcp creates a fresh transport (no session state)
Loxone Cloud Connect: resolves current tunnel URL via
dns.loxonecloud.comon every requestStructure cache: Loxone app structure (
LoxAPP3.json) cached for 60 seconds
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Control a Loxone Miniserver smart home: lights, blinds, climate, scenes and energy.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
BeautySpark MCP server for ChatGPT, Claude and other MCP clients
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server for Home Assistant — 202 tools across 21 domains; full control of your smart home from Claude / Cursor / VS Code / any MCP client34916MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language control of Loxone smart home systems, including lighting, audio, climate, and environmental monitoring, through MCP-compatible clients.41 npm3AGPL 3.0
- AlicenseAqualityDmaintenanceAn unofficial MCP (Model Context Protocol) server that exposes a Vaillant heat pump's data to AI assistants like Claude. Query outdoor and room temperatures, hot water status, energy consumption, COP estimates, schedules, and diagnostics through natural conversation.4MIT
- AlicenseNot gradedqualityDmaintenanceA zero-dependency local proxy that provides a stable, headless connection to a Loxone Miniserver's MCP Server, enabling control and monitoring of Loxone smart home via natural language.3MIT