Skip to main content
Glama
Disane87

weishaupt-wem-mcp-server

by Disane87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to weishaupt-wem-mcp-server

No user-submitted related servers found.

    Related Servers

    • emsesp-mcp-server by bosch-buderus-wp

      emsesp-mcp-serverofficial

      bosch-buderus-wp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM applications to query and visualize data from Bosch/Buderus heat pumps via ems-ESP, including temperatures, statistics, and heat curves through natural language.
      9
      MIT

    • Home Assistant MCP Server

      mjrestivo16
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.
      1
      MIT

    • victron-tcp

      lubosstrejcek
      A
      license
      A
      quality
      A
      maintenance
      Connect 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.
      32
      29 npm
      5
      MIT

    • unofficialMCP4Vaillant

      holger1411
      A
      license
      A
      quality
      D
      maintenance
      An unofficial MCP (Model Context Protocol) server that exposes a Vaillant heat pump's data to AI assistants like Claude. Query outdoor and room temperatures, hot water status, energy consumption, COP estimates, schedules, and diagnostics through natural conversation.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation3/5

    Five of eight tools are read-oriented and overlap substantially: wem_get_parameters explicitly 'combines metadata + refresh + read', which duplicates wem_get_parameter_meta and wem_read_parameters, while wem_get_overview and wem_get_writable_parameters are largely views/filters over the same data. The descriptions do clarify scope (device-wide vs module-wide vs specific params vs writable-only), preventing total confusion, but an agent must read carefully to pick correctly.

    Naming Consistency4/5

    All tools use a clean wem_<verb>_<noun> snake_case pattern. The only blemish is inconsistent verb choice for the same operation: wem_get_parameters vs wem_read_parameters vs wem_get_parameter_meta, which mixes 'get' and 'read' for parameter retrieval.

    Tool Count4/5

    Eight tools is a reasonable, well-scoped size for a device-control server. However, the read surface (overview, all parameters, specific parameters, writable parameters, metadata) could likely be consolidated to 2-3 tools, so a couple of tools do not fully earn their place.

    Completeness4/5

    The lifecycle is well covered: device discovery, status, parameter metadata, reading values, and writing values form a complete read/inspect/write loop. Minor gaps remain: no batch write for multiple parameters, and no alarm/fault/error diagnostics beyond connection status.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources