Skip to main content
Glama
NemoN

PLENTICORE MCP

by NemoN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PLENTICORE MCP

No user-submitted related servers found.

    Related Servers

    • solax-cloud-mcp

      mouldiwarp
      A
      license
      A
      quality
      D
      maintenance
      Provides real-time access to solar inverter data from the SolaX Cloud API, enabling queries of power output, energy yields, battery status, and grid import/export data.
      2
      MIT

    • Alpha ESS MCP Server

      michaelkrasa
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Alpha ESS solar inverter and battery system data, enabling monitoring of energy statistics, real-time power data, and configuration of battery charging and discharge schedules through the Alpha ESS Open API.
      10
      MIT

    • Growatt MCP Server

      ratoshniuk
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to monitor and control Growatt solar installations via the ShineServer API, including reading PV generation, load, grid import/export, battery SOC, and adjusting inverter settings.
      26
      MIT

    • sigenergy-mcp

      aydho
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      12
      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
    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 11 tools

    Disambiguation4/5

    The list_* discovery tools are clearly separated from the read_* tools by description (discover IDs vs read explicit IDs), and battery/energy/events/status each target distinct data. The only soft overlap is plenticore_overview, which aggregates battery, PV, meter and AC readings that plenticore_battery and plenticore_energy also expose, so an agent may occasionally choose overview redundantly.

    Naming Consistency4/5

    All names use a consistent plenticore_ prefix with snake_case, and the list_/read_/update_ verb pattern is applied predictably to processes and settings. The single-word resource reads (battery, energy, events, overview, status) deviate from the verb_noun pattern but remain unambiguous.

    Tool Count5/5

    Eleven tools is well within the ideal range for an inverter integration and each earns its place: discovery, targeted reads, an aggregate overview, and a single guarded write path. Nothing appears padded or redundant enough to be dropped.

    Completeness4/5

    The surface covers discovery, reads of measurements/energy/events/status, and settings read plus a dry-run-first write, which is a full lifecycle for this domain. Minor gaps exist: no process-data write, no setting pagination noted, and no explicit way to acknowledge or clear events, though these may be limitations of the inverter API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources