Skip to main content
Glama
ratoshniuk

Growatt MCP Server

by ratoshniuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Growatt MCP Server

No user-submitted related servers found.

    Related Servers

    • solax-cloud-mcp

      mouldiwarp
      A
      license
      A
      quality
      B
      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

    • anker-solix-mcp

      gkoenig
      A
      license
      A
      quality
      B
      maintenance
      Enables LLM agents to query live data from Anker Solix solar systems (Solarbank, expansion batteries, Smartmeter) via natural language, such as current solar production or battery state of charge.
      12
      1
      MIT

    • Powerline

      EdidiongA
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables conversational home power management by providing real-time solar, battery, and grid status, plus forecasts to answer questions like whether you can run an appliance. It supports Victron and Growatt inverters, remembers household appliances and grid events, and renders an interactive dashboard card in MCP-compatible clients.
      4 npm
      MIT

    • Fronius MCP Server

      huber
      A
      license
      A
      quality
      D
      maintenance
      Enables access to Fronius solar inverter data via the MCP protocol, allowing real-time monitoring of energy production, consumption, and battery storage through natural language.
      14
      8 npm
      4
      MIT

    • fronius-mcp

      flowiesner
      A
      license
      A
      quality
      D
      maintenance
      Enables real-time solar data from Fronius inverters via Claude, allowing natural language queries about solar production, battery, and grid exchange.
      5
      1
      Apache 2.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

    B3.4/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have distinct targets: plant details, plant data, plant energy, device info, dataloggers, users, and MAX-series inverters are clearly separated. A few pairs like get_plant_details vs get_plant_data and get_device_last_data vs get_max_data could be confused, but the descriptions disambiguate them well enough.

    Naming Consistency3/5

    The dominant get_* pattern is clear, but there is a mix of list_users, check_user, read_device_parameter, add_*, set_*, modify_*, and register_user. The inconsistent use of list vs get for listing resources and get vs read vs check makes the naming readable but not fully predictable.

    Tool Count2/5

    At 26 tools, the server is beyond the 25-tool threshold for a heavy surface. It covers many subdomains, but the count is high enough that agents will need to filter through many similar-looking operations.

    Completeness3/5

    The server covers plant creation/modification, device monitoring and control, user management, and MAX-specific operations. Notable lifecycle gaps exist: there are no remove/delete operations for plants, users, dataloggers, or storage devices, and some user update coverage is minimal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources