Larnitech vs Loxone AI
A side-by-side look at the Larnitech and Loxone AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
Loxone AIHome AutomationControl a Loxone Miniserver smart home: lights, blinds, climate, scenes and energy.37FairAuth: not declaredVerdict: choose Larnitech for home automation work as a local process; choose Loxone AI for home automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Larnitech when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
LChoose Loxone AI when
- You need dedicated capabilities in the Home Automation domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Loxone AI | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Larnitech | View Loxone AI |
Tools & capabilities
Larnitech tools
No tool names declared yet. Check the project README from the listing page.
Loxone AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Larnitech
{
"mcpServers": {
"larnitech": {
"command": "uvx",
"args": [
"larnitech-mcp"
]
}
}
}
Loxone AI
No confirmed install command for Loxone AI yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Larnitech is categorized under Home Automation and uses a local stdio subprocess. Loxone AI belongs to Home Automation and uses an install path we have not confirmed yet. Pick Larnitech for home automation work and Loxone AI for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Loxone AI has no confirmed install command yet — follow its own setup instructions.
Larnitech has no declared pricing — check the project's own site. Loxone AI has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add larnitech and loxone-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Larnitech has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Loxone AI has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.