openhab
Related Servers
Alternatives to openhab
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceServer that connects MCP (Multi-Capability Platform) with OpenHAB REST API, allowing MCP to interact with OpenHAB items through operations like getItemState and sendCommand.-
- AlicenseBqualityDmaintenanceMCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.66151 npmMIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server exposing the OpenAI platform REST API as tools for file management, fine-tuning, inference, images, audio, batch processing, and organization usage/costs.-
- AlicenseNot gradedqualityBmaintenanceA thin MCP server that securely enables AI agents to interact with Home Assistant, Mealie, and Nirvana via tools for automation, recipe management, and task tracking, while keeping credentials hidden.MIT
- AlicenseAqualityBmaintenanceAn MCP server that connects to Z-Wave JS UI's WebSocket to expose controller, node, and configuration information as tools for AI assistants to manage Z-Wave networks.241MIT
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server that exposes API endpoints as tools for AI assistants, using SSE transport.-
TDQS
Scored across 25 tools
Several tools overlap in practice: query_items vs resolve_item, initial_discovery vs get_system_summary vs generate_home_blueprint, and analyze_home vs diagnose_item vs remediate semantic fixes. The descriptions try hard to disambiguate with explicit 'PRIMARY' and 'do NOT use' warnings, which helps but also signals genuine boundary confusion.
Most names follow a predictable snake_case verb_noun or manage_/query_ pattern (manage_item, query_things, send_command, execute_batch). Minor deviations like remediate, automation, initial_discovery, and mcp_status are readable but break the pattern slightly.
At 25 tools, the surface is at the heavy end, and many tools are large action multiplexers with 5-15 actions each. The domain is broad, but overlapping discovery, query, and analysis tools make the count feel excessive rather than tightly scoped.
Coverage is broad and lifecycle-complete across items, things, rules, links, scenes, persistence, logs, UI, system config, media control, and automation generation. No obvious core OpenHAB operation appears missing.