MCP Loxone MCP Server

MCP Loxone MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Control your Loxone smart home through the Model Context Protocol.

What you get

• 🔌 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

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once MCP Loxone is connected, these are the calls the assistant has available:

• Category — Tools
• Lighting — control_light
• Blinds — control_blind
• Climate — set_temperature
• Security — set_security_mode
• Doors — control_door_lock
• Intercom — control_intercom
• Audio — control_audio
• Scenes — activate_scene
• General — control_device, get_*_status
• Requirements — The Requirements tool exposed by this server
• Binaries — The Binaries tool exposed by this server

Configuration and credentials

You will need 6 environment variables: LOXONE_HOST, LOXONE_USER, LOXONE_PASS, INFISICAL_PROJECT_ID, INFISICAL_CLIENT_ID, INFISICAL_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Loxone.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp loxone mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Loxone's toolset — Category, Lighting, Blinds and 9 more — is a fair guide to whether it matches your workflow. It is maintained by avrabe; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.