mcp-loxone

An opinionated Model Context Protocol (MCP) server for controlling Loxone home automation systems.

34 stars RustOthers Updated Aug 6, 2026

loxonemcpmcp-serverpython

Documentation

An async Rust MCP server that connects AI assistants to Loxone Miniservers. Control lights, blinds, climate, security, audio, and more — all through standardized MCP tools and resources.

> [!NOTE]

> Built on the PulseEngine MCP framework v0.17.0 for standardized protocol handling, authentication, and transport layers.

Features

🔌 17 MCP Tools — Control lights, blinds, HVAC, security, audio, door locks, intercoms, and scenes — all wired to real Miniserver commands
📊 25+ MCP Resources — Read-only access to rooms, devices, sensors, energy, weather, and system status with live state
🚀 Three Transports — stdio (Claude Desktop), HTTP/SSE (n8n, web clients), and Streamable HTTP
🔐 Security by Default — SSL verification on, UUID validation, rate limiting, input sanitization, dev-mode restricted to localhost
⚡ Async Rust — Connection pooling, intelligent caching, batch operations
🧊 Nix Flake — Reproducible builds with OpenClaw plugin integration
🔑 Credential Management — Credential ID system, environment variables, or Infisical vault

Quick Start

bash

# Build
cargo build --release

# Setup credentials
cargo run --bin loxone-mcp-setup -- --generate-id --name "My Home"

# Run with Claude Desktop
cargo run --bin loxone-mcp-server -- stdio --credential-id

Installation

From Source

bash

git clone https://github.com/avrabe/mcp-loxone
cd mcp-loxone
cargo build --release

Nix Flake

bash

nix build github:avrabe/mcp-loxone
# Or run directly
nix run github:avrabe/mcp-loxone

Docker

bash

docker build -t loxone-mcp .
docker run -e LOXONE_HOST=192.168.1.100 \
           -e LOXONE_USER=admin \
           -e LOXONE_PASS=secret \
           -p 3001:3001 loxone-mcp

Configuration

Credential ID (Recommended)

bash

# Interactive setup — generates a unique credential ID
cargo run --bin loxone-mcp-setup -- --generate-id --name "Main House"

# Or store manually
cargo run --bin loxone-mcp-auth -- store \
  --name "Office" --host 192.168.1.100 \
  --username admin --password secure123

# Manage credentials
cargo run --bin loxone-mcp-auth -- list
cargo run --bin loxone-mcp-auth -- test

Environment Variables

bash

export LOXONE_HOST="192.168.1.100"
export LOXONE_USER="admin"
export LOXONE_PASS="password"

Infisical Vault (Production)

bash

export INFISICAL_PROJECT_ID="your-project-id"
export INFISICAL_CLIENT_ID="your-client-id"
export INFISICAL_CLIENT_SECRET="your-client-secret"

> [!TIP]

> Migrating from environment variables? See the Credential Migration Guide.

Usage

Claude Desktop

Add to your `claude_desktop_config.json`:

json

{
  "mcpServers": {
    "loxone": {
      "command": "loxone-mcp-server",
      "args": ["stdio", "--credential-id", "abc123def-456-789"]
    }
  }
}

HTTP Server (n8n, MCP Inspector)

bash

# Standard HTTP/SSE
loxone-mcp-server http --port 3001 --credential-id 

# Streamable HTTP (new MCP Inspector)
loxone-mcp-server streamable-http --port 3001 --credential-id

OpenClaw Integration

The flake exports an `openclawPlugin` for nix-openclaw:

nix

customPlugins = [
  {
    source = "github:avrabe/mcp-loxone";
    config.env = {
      LOXONE_HOST = "/path/to/secrets/loxone-host";
      LOXONE_USER = "/path/to/secrets/loxone-user";
      LOXONE_PASS = "/path/to/secrets/loxone-pass";
    };
  }
];

Tools & Resources

Tools (Actions)

Category	Tools	Description
Lighting	`control_light`	On/off, dim 0-100%
Blinds	`control_blind`	Up/down/stop, position 0-100%
Climate	`set_temperature`	Target temperature with safe range validation
Security	`set_security_mode`	Arm, disarm, night, away modes
Doors	`control_door_lock`	Lock, unlock, open
Intercom	`control_intercom`	Answer, decline, open door
Audio	`control_audio`	Play, pause, volume per zone
Scenes	`activate_scene`	Trigger named scenes
General	`control_device`, `get_*_status`	Direct device control, live status queries

Resources (Read-Only)

URI Pattern	Data
`loxone://rooms`	Room listing with device counts
`loxone://rooms/{room}/devices`	Devices in a specific room
`loxone://devices/all`	Full device inventory
`loxone://devices/category/{cat}`	Devices by category
`loxone://sensors/*`	Door/window, temperature, motion
`loxone://audio/zones`	Audio zone configuration
`loxone://system/status`	Miniserver status and capabilities
`loxone://energy/*`	Power monitoring and consumption

Architecture

code

AI Assistant (Claude, n8n, OpenClaw)
        │
   MCP Protocol (stdio / HTTP / Streamable HTTP)
        │
   ┌────▼─────────────────────────┐
   │   loxone-mcp-server          │
   │  ┌─────────────────────────┐ │
   │  │ Security Layer          │ │
   │  │ Auth · Rate Limit · TLS │ │
   │  ├─────────────────────────┤ │
   │  │ Tool Handlers           │ │
   │  │ 17 tools → send_command │ │
   │  ├─────────────────────────┤ │
   │  │ Loxone Client           │ │
   │  │ HTTP · WebSocket · Cache│ │
   │  └─────────────────────────┘ │
   └────┬─────────────────────────┘
        │
   HTTP /jdev/sps/io/{uuid}/{cmd}
        │
   Loxone Miniserver
        │
   Physical Devices

Development

Requirements

Rust 1.85+ (2024 edition)
Loxone Miniserver (Gen 1 or Gen 2)

Building & Testing

bash

cargo build                                    # Dev build
cargo test --lib                               # Unit tests
cargo fmt && cargo clippy -- -D warnings       # Format + lint
cargo audit                                    # Security audit

Live Miniserver Testing

bash

# Requires network access to Miniserver
LOXONE_LIVE_TEST=1 cargo test \
  --test live_miniserver_tests \
  --features test-utils -- --nocapture

Project Structure

code

src/
├── server/          # MCP protocol, tool handlers (macro_backend.rs)
├── client/          # HTTP/WebSocket clients with UUID validation
├── config/          # Credentials, master key auto-persistence
├── security/        # Input sanitization, rate limiting, CORS
├── monitoring/      # Metrics, dashboards, InfluxDB
├── history/         # Time-series data storage
├── discovery/       # mDNS network discovery
└── main.rs          # CLI, transport selection, startup

Binaries

Binary	Purpose
`loxone-mcp-server`	Main MCP server (stdio/HTTP/streamable-http)
`loxone-mcp-auth`	Credential management (store, list, test, delete)
`loxone-mcp-setup`	Interactive setup with credential ID generation
`loxone-mcp-test-endpoints`	API endpoint testing (development)

License

Licensed under either of:

at your option.

Frequently asked questions

What is mcp-loxone?

mcp-loxone is An opinionated Model Context Protocol (MCP) server for controlling Loxone home automation systems.

How do I install mcp-loxone?

Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.

Is mcp-loxone open source?

Yes — it is hosted on GitHub at https://github.com/avrabe/mcp-loxone and has 34 stars.

Related MCP tools

webclaw

Fast, local-first web content extraction for LLMs. Scrape, crawl, extract structured data — all from Rust. CLI, REST API, and MCP server.

2,319 Rust

ai-agentsclillm+17

OpenOSINT

AI-powered OSINT agent with interactive REPL, MCP server, and CLI. 19 tools. Works with Claude, GPT-4, or local models. For authorized security research only.

1,523 Python

ai-agentanthropicclaude+16

projectmem

Open-source coding agent memory. Records issues, attempts, fixes and decisions, then warns your agent before it repeats an approach that already failed. Native MCP server for Claude Code, Cursor, Antigravity and Codex. 100% local, no cloud, no telemetry. MIT.

796 Python

ai-agentsai-memoryai-tools+17

goose

an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM

53,903 Rust

mcpacpai+1

screenpipe

YC (S26) | Open Computer History | Record your screen continuously locally and provide context to your agents (Claude, Codex, Openclaw, Hermes, Runner...)

21,409 Rust

aicomputer-visionllm+17

fff

The fastest and the most accurate file search SDK for AI agents, Neovim, Rust, C, Python, Bun and NodeJS

10,397 Rust

filesearchluaneovim+8

Run your own MCP server? See who uses it and what to fix.

Measure it with TrackMCP