Skip to main content
Glama
fronius-mcp

fronius-mcp

by flowiesner

fronius-mcp

PyPI MCP Registry

Real-time solar data from your Fronius inverter, directly in Claude.

Ask things like:

"How much solar power am I generating right now?"

"What's my battery charge level?"

"Am I currently importing or exporting to the grid?"

"How much energy did I produce this year?"

"What can you do with my solar system?"

"Analyse my photovoltaics for me."

Connects to the Fronius Solar API v1 directly on your local network — no cloud account, no subscription, no data leaving your home.


How it works

fronius-mcp is a Model Context Protocol (MCP) server. MCP is an open standard that lets AI assistants like Claude connect to external tools and data sources. Once configured, Claude can call your inverter's local API in real time — whenever you ask a question about your solar system, Claude fetches live data and answers based on what's actually happening right now.


Related MCP server: Enphase Solar MCP Server

Requirements

  • A Fronius inverter on your local network with the Solar API (JSON API) enabled

  • Claude Desktop

  • uv — a fast Python package manager (one-line install)


Setup

1. Install uv

uv is a fast Python package manager used to run fronius-mcp without a permanent install.

macOS / Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

Windows (PowerShell):

irm https://astral.sh/uv/install.ps1 | iex

Restart your terminal after installing.

2. Add to Claude Desktop

Open your claude_desktop_config.json and add the fronius block inside mcpServers:

{
  "mcpServers": {
    "fronius": {
      "command": "uvx",
      "args": ["fronius-mcp"]
    }
  }
}

Config file location:

Platform

Path

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

Windows (Store app)

%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json

Tip: If the mcpServers key already exists, just add the fronius block inside it — don't create a second mcpServers.

3. Restart Claude Desktop

Close and reopen Claude Desktop so it picks up the new server config.

4. Configure your inverter

In a new Claude conversation, say:

"Configure my Fronius inverter at 192.168.178.35"

Claude will save your inverter's IP and confirm the connection. This is a one-time step — the address is stored in ~/.fronius-mcp.json and persists across restarts.

Don't know your inverter's IP? Tell Claude: "I want to configure my Fronius inverter but I don't know the IP." Claude will walk you through finding it via your router, Fronius Solar.web, or the inverter's touch display — and how to enable the Solar API in the inverter's web interface if you haven't done that yet.


What you can ask

Once set up, just talk to Claude naturally. Some examples:

  • "What's my current solar output?" — live PV generation in watts

  • "How self-sufficient am I right now?" — autonomy and self-consumption percentages

  • "Is my battery charging or discharging?" — battery power flow and state of charge

  • "How much have I fed into the grid today?" — energy totals from the smart meter

  • "What devices are connected to my inverter?" — full system topology

  • "Give me a full overview of my solar system." — Claude combines all data sources into a summary


Tools

Tool

What it does

configure_inverter

Set your inverter's IP address — run this once on first setup

solar_power_flow

PV generation, grid exchange, house load, battery power, autonomy, energy totals

solar_meter

Grid power per phase, cumulative energy in/out, voltage, current, frequency

solar_battery

State of charge, voltage, current, temperature, capacity, status

solar_devices

All connected devices with type, bus index, and serial number


Compatible Hardware

Developed and tested on:

  • Fronius Symo GEN24 10.0 Plus

  • BYD Battery-Box Premium HV (13.824 kWh)

  • Fronius Smart Meter (grid feed-in point, 3-phase)

Other Fronius inverters with Solar API v1 support should work. Some API endpoints behave differently across models — if something doesn't work on your hardware, open an issue.


License

Apache 2.0 — see LICENSE.

Available Tools

5 tools
configure_inverterA

Configure the Fronius inverter IP address or hostname.

Call this once to tell the MCP server where your inverter lives. The value is saved to ~/.fronius-mcp.json and persists across restarts.

Also returns instructions for finding the inverter IP and enabling the Solar API — useful for first-time setup.

Args: host: IP address or hostname of the inverter (e.g. '192.168.178.35'). Scheme and port are stripped automatically.

Returns a confirmation message plus setup instructions, or a connectivity warning if the inverter cannot be reached.

Inputs: host (required). Returns: result

solar_batteryA

Real-time data from the BYD Battery-Box Premium HV.

Returns state of charge (soc_pct), DC voltage and current, cell temperature (temp_c), usable and design capacity in Wh, cell status, enabled flag, and manufacturer/model info.

Inputs: no named parameters.

solar_devicesA

Lists all devices currently connected to the Fronius inverter system.

Returns a dict with device classes (inverter, meter, storage, ohmpilot, etc.) as keys. Each entry is a list of connected devices with their bus index and serial number. Empty list means the device class is supported but nothing is connected. Useful for verifying system topology or diagnosing missing devices.

Inputs: no named parameters.

solar_meterA

Real-time data from the Fronius Smart Meter at the grid feed-in point.

Returns total grid power (power_w), per-phase real power (power_l1/l2/l3_w), total energy consumed from grid (energy_consumed_wh), total energy fed into grid (energy_fed_wh), per-phase voltage and current (voltage/current_l1/l2/l3), and grid frequency (frequency_hz). Positive power = importing from grid, negative = exporting to grid.

Inputs: no named parameters.

solar_power_flowA

Real-time power flow data from the Fronius Symo GEN24 inverter.

Returns PV generation (pv_w), grid exchange (grid_w, positive = import, negative = export), house load (load_w), battery power (battery_w, positive = charging, negative = discharging), autonomy and self-consumption percentages, daily/yearly/total energy yields, operating mode, and battery standby state.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      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).
      18
      13
      MIT
    • 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
    • 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
      12 npm
      4
      MIT
    • A
      license
      A
      quality
      C
      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