Loxone MCP Server
Enables natural language control of Loxone smart home systems, including lighting, audio, climate, and environmental monitoring, through MCP-compatible clients.
README
Loxone MCP Server
A Model Context Protocol (MCP) server for Loxone home automation integration.
Real-Life Usage Example
See how this MCP server integrates with Claude Desktop for smart home control: Claude Desktop Demo
Temporarily disabled ventilation and asked to analyze air quality impact and generate comprehensive indoor climate reports.
- Lighting Control: Adjust lights throughout your home with natural language commands
- Audio Management: Control multi-room audio systems and zones
- Climate Control: Manage ventilation, heating, and cooling systems
- Environmental Monitoring: Generate reports on indoor climate conditions (temperature, humidity, CO2 levels)
Quick usage guide
Using npm package
To use npm package, minimum nodejs 20 is required.
First install the package globally:
npm install -g @reijosirila/loxone-mcp-server
Add to your Claude claude_desktop_config.json or any other MCP client config:
{
"mcpServers": {
"loxone": {
"command": "loxone-mcp-server",
"env": {
"LOXONE_HOST": "192.168.1.100",
"LOXONE_USERNAME": "your-username",
"LOXONE_PASSWORD": "your-password"
}
}
}
}
Using Docker Hub image
First pull the image:
docker pull reijosirila/loxone-mcp-server
Then add to your Claude claude_desktop_config.json or any other MCP client config:
{
"mcpServers": {
"loxone": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-e", "LOXONE_HOST",
"-e", "LOXONE_USERNAME",
"-e", "LOXONE_PASSWORD",
"reijosirila/loxone-mcp-server"
],
"env": {
"LOXONE_HOST": "192.168.1.100",
"LOXONE_USERNAME": "your-username",
"LOXONE_PASSWORD": "your-password"
}
}
}
}
Loxone Statistics Support
The MCP server supports Loxone Statistics, which aggregates historical data into smaller portions optimized for AI analysis. This allows for efficient analysis of trends and patterns in your smart home data.
- Statistics V1: ✅ Fully supported and tested
- Statistics V2: ⚠️ Supported but not yet tested
Loxone Control Implementation Status
| Control | Implemented | Support Level | Tested |
|---|---|---|---|
| Implemented Controls | |||
| Alarm | ✅ | Full | ❌ |
| AudioZone | ✅ | Full | ✅ |
| AudioZoneV2 | ✅ | Full | ✅ |
| Central Objects (Alarm) | ✅ | Full | ❌ |
| Central Objects (AudioZone) | ✅ | Full | ✅ |
| Central Objects (Gate) | ✅ | Full | ❌ |
| Central Objects (Jalousie) | ✅ | Full | ❌ |
| Central Objects (Window) | ✅ | Full | ❌ |
| ColorPicker | ✅ | Full | ✅ |
| ColorPickerV2 | ✅ | Full | ✅ |
| Dimmer | ✅ | Full | ✅ |
| EIBDimmer | ✅ | Full | ✅ |
| Gate | ✅ | Full | ❌ |
| InfoOnlyAnalog | ✅ | Full | ✅ |
| InfoOnlyDigital | ✅ | Full | ✅ |
| Intelligent Room Controller | ✅ | ⚠️ Partial | ❌ |
| Intelligent Room Controller v2 | ✅ | ⚠️ Partial | ✅ |
| Jalousie | ✅ | Full | ❌ |
| LightController | ✅ | Full | ✅ |
| LightControllerV2 | ✅ | Full | ✅ |
| Meter | ✅ | Full | ✅ |
| Pushbutton | ✅ | Full | ✅ |
| Radio | ✅ | Full | ✅ |
| Slider | ✅ | Full | ✅ |
| Switch | ✅ | Full | ✅ |
| TextState | ✅ | Full | ✅ |
| EnergyFlowMonitor | ✅ | Full | ✅ |
| EnergyManager2 | ✅ | Full | ❌ |
| IntercomV2 | ✅ | Full | ❌ |
| Sauna | ✅ | Full | ❌ |
| Not Implemented Controls | |||
| AalEmergency | ❌ | - | ❌ |
| AalSmartAlarm | ❌ | - | ❌ |
| ACControl | ❌ | - | ❌ |
| AlarmChain | ❌ | - | ❌ |
| AlarmClock | ❌ | - | ❌ |
| Application | ❌ | - | ❌ |
| CarCharger | ❌ | - | ❌ |
| ClimateController | ❌ | - | ❌ |
| ClimateControllerUS | ❌ | - | ❌ |
| Daytimer | ❌ | - | ❌ |
| EnergyManager | ❌ | - | ❌ |
| Fronius | ❌ | - | ❌ |
| Heatmixer | ❌ | - | ❌ |
| Hourcounter | ❌ | - | ❌ |
| InfoOnlyText | ❌ | - | ❌ |
| Intercom | ❌ | - | ❌ |
| Irrigation | ❌ | - | ❌ |
| LightsceneRGB | ❌ | - | ❌ |
| LoadManager | ❌ | - | ❌ |
| MailBox | ❌ | - | ❌ |
| MsShortcut | ❌ | - | ❌ |
| NFC Code Touch | ❌ | - | ❌ |
| PoolController | ❌ | - | ❌ |
| PowerUnit | ❌ | - | ❌ |
| PresenceDetector | ❌ | - | ❌ |
| PulseAt | ❌ | - | ❌ |
| Remote | ❌ | - | ❌ |
| Sequential | ❌ | - | ❌ |
| SmokeAlarm | ❌ | - | ❌ |
| SolarPumpController | ❌ | - | ❌ |
| SpotPriceOptimizer | ❌ | - | ❌ |
| StatusMonitor | ❌ | - | ❌ |
| SteakThermo | ❌ | - | ❌ |
| SystemScheme | ❌ | - | ❌ |
| TextInput | ❌ | - | ❌ |
| TimedSwitch | ❌ | - | ❌ |
| Tracker | ❌ | - | ❌ |
| UpDownLeftRight (analog) | ❌ | - | ❌ |
| UpDownLeftRight (digital) | ❌ | - | ❌ |
| ValueSelector | ❌ | - | ❌ |
| Ventilation | ❌ | - | ❌ |
| Wallbox2 | ❌ | - | ❌ |
| WallboxManager | ❌ | - | ❌ |
| Webpage | ❌ | - | ❌ |
| Window | ❌ | - | ❌ |
| WindowMonitor | ❌ | - | ❌ |
Adding New Controls
Implementing new controls is straightforward using the AbstractControlType base class. Each control type follows a consistent pattern, making it easy to add support for additional Loxone controls.
📚 Loxone Official Documentation: Loxone Structure File Documentation
Contributions are welcome! If you need a control that's not yet implemented, feel free to submit a pull request.
Miniserver Version Support
- Miniserver v1: ✅ Fully supported (local and remote connections)
- Miniserver v2: ⚠️ Local connection only
- v2 should work but is not tested
- Remote connection to v2 is not currently supported due to SSL encryption requirements
- The underlying client library (
loxone-ts-api) doesn't have SSL support implemented yet
🙏 Special thanks to the loxone-ts-api library for providing the foundation for Loxone communication!
Supported MCP Transports
- Stdio: ✅ Fully supported
- HTTP: ✅ Fully supported (Express server with
/mcpendpoint)
The transport can be configured using the MCP_TRANSPORT environment variable:
stdio(default): Standard input/output transporthttp: HTTP server with Streamable HTTP support at/mcpendpoint
Connection Options
-
Connect directly to your Miniserver using its local IP address.
-
Connect to your Miniserver remotely using Loxone's cloud discovery service:
- Automatically discovers your Miniserver's external URL and port using its serial number. This is done using HEAD request to:
https://dns.loxonecloud.com/<sn> - Loxone External Access must be enabled.
- Automatically discovers your Miniserver's external URL and port using its serial number. This is done using HEAD request to:
Local Docker Setup
Building the Docker Image
git clone git@github.com:reijosirila/loxone-mcp-server.git
cd loxone-mcp-server
docker build -t loxone-mcp-server .
Environment Variables
You can also create a .env file with your Loxone credentials and configuration:
# Loxone connection settings
LOXONE_HOST=192.168.1.100
LOXONE_USERNAME=admin
LOXONE_PASSWORD=your-password
# Or connect over the internet using Loxone DNS
# This will auto-discover Loxone external URL and port
# LOXONE_SERIAL_NUMBER=
# MCP Transport configuration
# Options: stdio (default), http
MCP_TRANSPORT=stdio
# HTTP server port (only used when MCP_TRANSPORT=http)
# Default: 3000
PORT=3000
# Log level (0=ERROR, 1=WARN, 2=INFO, 3=DEBUG)
# Default: 1 for stdio, 2 for http
LOG_LEVEL=2
Alternative: Running without Docker
If you prefer to run without Docker, you can use Node.js directly:
{
"mcpServers": {
"loxone": {
"command": "node",
"args": ["dist/server.js"],
"cwd": "/path/to/loxone-mcp-server",
"env": {
"LOXONE_HOST": "your-loxone-ip",
"LOXONE_USERNAME": "your-username",
"LOXONE_PASSWORD": "your-password"
}
}
}
}
Development
Prerequisites
- Node.js 22+
- npm
- TypeScript
Installation
# Installation
npm install
# Build
npm run build
# Run with stdio transport (default)
npm start
# Run with HTTP transport
MCP_TRANSPORT=http npm start
# or
npm run start:http
# Development mode
npm run dev # stdio transport
npm run dev:http # Streamable HTTP transport
Streamable HTTP Transport Usage
When using Streamable HTTP transport, the server listens on port 3000 by default (configurable via PORT or MCP_PORT environment variable):
- MCP Endpoint:
http://localhost:3000/mcp - Health Check:
http://localhost:3000/health(no authentication required)
API Key Authentication
The Streamable HTTP server supports optional API key authentication via the MCP_API_KEY environment variable:
# Set API key for secure access
MCP_API_KEY=your-secure-api-key-here MCP_TRANSPORT=http npm start
When configured, the API key can be provided in two ways:
- Bearer Token:
Authorization: Bearer your-secure-api-key-here - X-API-Key Header:
X-API-Key: your-secure-api-key-here
If MCP_API_KEY is not set, the server will be publicly accessible (useful for development or when behind a reverse proxy).
Internet Access Security
⚠️ Important: If you're exposing the HTTP server over the internet, always use SSL offload with a reverse proxy (e.g., nginx) to secure the connection.
Example Claude Desktop/Gemini configuration for HTTP transport:
{
"mcpServers": {
"loxone-http": {
"httpUrl": "http://localhost:3000/mcp",
"description": "Loxone Smart Home MCP Server (HTTP)"
}
}
}
Example with API key authentication (when connecting to a remote server):
{
"mcpServers": {
"loxone-http-secure": {
"httpUrl": "https://your-server.com/mcp",
"headers": {
"Authorization": "Bearer your-secure-api-key-here"
},
"description": "Loxone Smart Home MCP Server (Secure HTTP)"
}
}
}
Or using X-API-Key header:
{
"mcpServers": {
"loxone-http-secure": {
"httpUrl": "https://your-server.com/mcp",
"headers": {
"X-API-Key": "your-secure-api-key-here"
},
"description": "Loxone Smart Home MCP Server (Secure HTTP)"
}
}
}
License
This software is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
Important License Terms
- ✅ Free to use for personal and commercial purposes
- ✅ Modifications allowed and encouraged
- ⚠️ Source code must be shared when:
- You distribute the software
- You use it as a network service (SaaS)
- You modify and deploy it commercially
For the full license text, see the LICENSE file.
Contributing
Contributions are welcome! By contributing to this project, you agree to license your contributions under the AGPL-3.0 license.
Support
For issues, feature requests, or questions, please open an issue on GitHub.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。