Skip to main content
Glama
aydho

sigenergy-mcp

by aydho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sigenergy-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • EG4 Entra MCP Lab

      jLuPSP
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Entra-authorized monitoring and control of an EG4 inverter via MCP, with OBO delegation and safety gates.
      MIT

    • EG4 MCP Server

      matt-dreyer
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for EG4 solar inverters, enabling real-time monitoring, performance analysis, battery health, alerts, maintenance insights, and historical data via natural language.
      22 PyPI
      MIT

    • solar-mcp

      vasilyevstan
      A
      license
      A
      quality
      B
      maintenance
      Exposes a single read-only tool that retrieves live Huawei SUN2000 inverter telemetry over local Modbus TCP, including model, firmware, active power, daily and lifetime yield, device status, and observation timing. Readings are briefly cached, with failures returned as errors rather than stale or fabricated values.
      1
      AGPL 3.0

    • viaris-mcp

      Nolex13
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor and control Orbis Viaris EV chargers over the local network, including live power status, charging schedules, history, and power limits, with no cloud dependency.
      12
      2 npm
      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.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool targets a distinct subsystem (plant, grid, battery, inverter, EV charger, energy totals, registers), so boundaries are mostly clear. The only mild overlap is that get_plant_status summarizes data also exposed by the individual status tools, but descriptions clarify the live-overview vs subsystem-detail distinction.

    Naming Consistency5/5

    Names follow a consistent verb_noun snake_case pattern (get_*_status, get_*_info, list_registers, read_registers, read_raw_registers, discover_devices). The verbs (get/list/read/discover) map predictably to action type.

    Tool Count5/5

    12 tools is well within the sweet spot for a monitoring/inspection domain, and each earns its place by covering a distinct device or data access layer.

    Completeness4/5

    The read surface is thorough: live status, static info, energy counters, settings, named-register and raw-register access, device discovery, and EV charging. The notable gap is write/control operations (e.g. setting power or SOC limits) implied by get_control_settings, though read_raw_registers partially mitigates unmapped reads.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources