mcp-loxone

This MCP server bridges a Loxone Miniserver environment with the MCP ecosystem. It exposes 17 action tools for controlling devices, lighting, blinds, climate, audio, security and workflows, as well as 25+ read-only resources for rooms, devices, system state, sensors, and more. The server supports both stdio (for Claude Desktop integration) and HTTP/SSE (for web clients). To run via HTTP, start the server in HTTP mode (port configurable) and use a credential-based authentication flow to access Miniserver credentials securely. Tools are designed as discrete actions (e.g., control_device, control_lights_unified, set_room_temperature) and resources provide structured data readouts (e.g., loxone://devices/all, loxone://rooms, loxone://system/status). When configuring clients, you can connect via MCP protocol over HTTP and subscribe to updates, enabling real-time status and data retrieval in your home automation automations.

To use Claude Desktop or other MCP clients, reference the server with a command that starts the HTTP MCP transport and supply a valid credential-id. For example, credentials can be managed locally and tested using the included loxone-mcp-auth tooling, and then used by the HTTP endpoint to authorize access to the Miniserver. The tooling supports listing credentials, testing connections, and storing new credentials, which simplifies large deployments across multiple sites.

Prerequisites:

• Rust toolchain (Rust 1.70+ as advertised)
• git
• Access to a Loxone Miniserver (Gen 1 or Gen 2) on the same network

From Source

1. Install Rust and Git if not already installed.
   • macOS/Linux: follow rustup.rs instructions
   • Windows: install rustup and cargo
2. Clone the repository and build

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

3. Run the server in HTTP mode (example port 3001)

# Once built, start the server (adjust path to binary as needed)
./target/release/loxone-mcp-server http --port 3001

Configuration with Credential ID (recommended)

# Start with HTTP transport and a credential-id obtained from the credential store
./target/release/loxone-mcp-server http --port 3001 --credential-id abc123def-456-789

Legacy environment variables (for reference)

export LOXONE_HOST="http://192.168.1.100"
export LOXONE_USER="admin"
export LOXONE_PASS="your-password"

Testing credentials

# List credentials
cargo run --bin loxone-mcp-auth list

# Test a credential
cargo run --bin loxone-mcp-auth test <credential-id>

Migration and updates

• If you previously used environment variables, consider migrating to Credential IDs as outlined in the repository's Credential Migration Guide.

Notes and tips:

• The server is built on the PulseEngine MCP framework and exposes 17 actions and 25+ read-only resources. Refer to the docs for tools and resources references.
• HTTP transport supports SSE and WebSocket-based updates; for web integrations, prefer the HTTP endpoint with proper authentication.
• If you enable credential-based authentication, ensure the credential-id you provide is stored and managed securely (prefer using the built-in loxone-mcp-auth tooling).
• Ports, credential sources, and connectivity to the Loxone Miniserver may require firewall adjustments or network routing changes.
• For production deployments, consider enabling TLS termination at a reverse proxy and using the Vault/Infisical integration described in security docs for secret management.