idm-mcp
Related Servers
Alternatives to idm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to read and write selected values from IDM heat pumps via Modbus TCP, providing controlled access to operational data and setpoints.3MIT
- AlicenseAqualityBmaintenanceEnables local monitoring and control of a Sigenergy energy system over Modbus TCP, exposing live solar, battery, grid, load and EV charger data plus optional write tools for remote EMS modes, power and SOC limits, grid import/export caps and EV charging — no cloud account required.12MIT
- AlicenseAqualityBmaintenanceControl and monitor Weishaupt heating systems via the WEM Portal with AI assistants, enabling device discovery, parameter reading/writing, and system overview.824 npmMIT
- AlicenseAqualityAmaintenanceConnect AI assistants to Victron Energy systems to read real-time solar, battery, grid, and inverter data from your local network via Modbus TCP or MQTT.3229 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables an LLM to read sensor values and control actuators on a Modbus TCP PLC, supporting both boolean and analog tags.4MIT
- FlicenseNot gradedqualityAmaintenanceMCP server that connects WAGO PLCs to LLM agents via the WDx/WDA REST API, enabling AI assistants to read sensor values, change configuration, trigger firmware updates, or monitor entire PLC fleets without custom code.45 PyPI4-
TDQS
Scored across 13 tools
Most tools are clearly distinct, but idm_health_check overlaps slightly with idm_get_system_status by reading similar values (Außentemperatur, Betriebsart, Summenstörung). The rest each target a unique subsystem or control aspect.
All tools follow a consistent idm_verb_noun pattern. Reads use get_, writes use set_, and health_check is a clear exception but still follows the prefix convention.
13 tools is within the ideal range for a device-specific server, covering both monitoring and control without being overwhelming or sparse.
Good lifecycle coverage for the heat pump domain: all major subsystems are readable, and key control actions (mode, smart grid, PV surplus, hot water setpoints, demand) are writable. Minor gap: no setters for heating circuit setpoints/curves, but that may be outside the server's scope.