About

mcp-loxone is a community Model Context Protocol server for connecting AI assistants to Loxone home automation systems. The repository describes an async Rust implementation that can control Loxone Miniservers through standardized MCP tools and expose read-only resources for rooms, devices, sensors, energy, weather, and system status.

This entry refers to the avrabe/mcp-loxone project, not the separate Loxone Config public beta feature named MCP Server for Miniserver. Loxone's own changelog documents native MCP Server plugin support in Config 17.1 public beta, so builders comparing options should distinguish the community Rust server from the vendor plugin.

Key Features

17 documented MCP tools for lighting, blinds, climate, security, doors, intercom, audio, scenes, direct device control, and status queries.
25+ documented MCP resources for rooms, room devices, all devices, device categories, sensors, audio zones, Miniserver status, and energy data.
Supports stdio for Claude Desktop, HTTP/SSE for n8n and web clients, and Streamable HTTP for newer MCP clients.
Runs as a Rust server with source builds, Docker deployment, Nix Flake support, and OpenClaw plugin integration.
Credential handling is documented through credential IDs, environment variables, or optional Infisical vault variables.

Use Cases

Let an MCP-capable assistant inspect rooms and devices before controlling lights, blinds, HVAC, locks, intercoms, audio zones, or scenes.
Connect Loxone status and control to Claude Desktop through stdio.
Expose a local or networked HTTP/SSE endpoint for automation tools, MCP Inspector, n8n-style workflows, or web clients.
Give an agent read-only context about sensors, energy usage, and system status while keeping command execution behind Loxone credentials.

Compatibility

Documented client and transport coverage is strongest for Claude Desktop over stdio, plus generic HTTP/SSE and Streamable HTTP clients. The README also names n8n, MCP Inspector, web clients, and OpenClaw integration. Public documentation does not provide first-party, client-specific setup blocks for Cursor, Codex, Windsurf, VS Code, or Lovable.

Limitations

A Loxone Miniserver and valid Miniserver credentials are required. The project is locally installed or self-hosted; it is not documented as a hosted SaaS MCP endpoint. Docker setup is documented, but the README's Docker example does not explicitly show a transport argument. The official Loxone Config MCP plugin is a separate vendor feature with limited public setup detail in the beta changelog.

Sources

GitHub repository: https://github.com/avrabe/mcp-loxone
Project site: https://avrabe.github.io/mcp-loxone/
Loxone Config public beta changelog: https://www.loxone.com/enen/support/loxone-config-public-beta/
MCP Market listing: https://mcpmarket.com/server/loxone-1
Smarteon lox-mcp comparison source: https://github.com/Smarteon/lox-mcp
Syntropic Loxone MCP comparison source: https://github.com/syntropicsignal-ai/loxone-mcp

MCP Setup

Prerequisites

Rust 1.85+ for development or source builds
Loxone Miniserver (Gen 1 or Gen 2)
Network access to the Loxone Miniserver
Loxone Miniserver host, username, and password
Docker or Nix are optional deployment paths

Access requirements

Loxone Miniserver credentials are required
No public OAuth flow is documented for this server
Credential IDs, environment variables, or Infisical vault variables can be used for secrets

Client setup

Claude Desktop

Transport: stdio

loxone-mcp-server stdio --credential-id abc123def-456-789

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

Build from source with cargo build --release or otherwise make the loxone-mcp-server binary available.
Create or store Loxone credentials and obtain a credential ID.
Add the documented mcpServers block to claude_desktop_config.json.
Restart Claude Desktop.

Auth:

Use a credential ID generated by loxone-mcp-setup or stored by loxone-mcp-auth.
Alternatively configure LOXONE_HOST, LOXONE_USER, and LOXONE_PASS as environment variables.

The README documents Claude Desktop stdio setup. No Claude Code-specific command is documented.