Skip to main content
Glama
flowiesner

fronius-mcp

by flowiesner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fronius-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      20 npm
      4
      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

    • REE MCP Server

      ESJavadex
      A
      license
      A
      quality
      C
      maintenance
      Enables natural language conversations with Spain's electrical grid data through Claude, providing real-time access to electricity demand, generation, prices, and emissions data from Red Eléctrica de España (REE).
      2
      18
      11
      MIT

    • Enphase Solar MCP Server

      xianman
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop to the Enphase Developer API v4 for read-only access to solar production, consumption, battery, and EV charger data, with optional write tools for battery settings and EV charging.
      1
      MIT

    • 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
    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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the solar system: configuration, battery, devices, meter, and power flow. No two tools have overlapping purposes.

    Naming Consistency4/5

    Most tools follow a 'solar_<noun>' pattern (solar_battery, solar_devices, solar_meter, solar_power_flow), but 'configure_inverter' breaks this pattern by using a verb + noun form instead.

    Tool Count5/5

    With 5 tools, the server covers essential monitoring operations (configuration, battery, devices, meter, power flow) without being bloated or too sparse.

    Completeness3/5

    Covers real-time monitoring well but lacks historical data retrieval or energy totals. Missing tools for writing settings (e.g., set battery mode) limits completeness for a full lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources