# fronius-mcp [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/flowiesner/fronius-mcp  
**GitHub Stars:** 1  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/fronius-mcp

## Description
Real-time Fronius inverter data in Claude — PV, battery, grid and smart meter via local Solar API.

## Tools
Capabilities this server exposes over MCP:

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

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

## Documentation

## What fronius-mcp MCP server does

The fronius-mcp MCP server exposes data from a Fronius inverter through the Model Context Protocol. It is intended for solar installations where an AI assistant needs current operating information from the local network. The server can report photovoltaic generation, household consumption, grid import or export, battery activity, autonomy, self-consumption, and energy totals.

It also exposes smart-meter readings, including per-phase grid power, cumulative energy entering or leaving the system, voltage, current, and frequency. Battery queries include state of charge, voltage, current, temperature, capacity, and status. A device inventory tool returns connected equipment with its type, bus index, and serial number.

## How it works

The server calls Fronius Solar API v1 directly on the local network. After the inverter address is configured, an MCP-compatible assistant can request current data when a user asks about the solar system. The data path remains local according to the project documentation; a cloud account or subscription is not required, and the inverter readings do not need to leave the home network for this connection.

The initial configuration uses `configure_inverter` to save the inverter IP address. That address is stored in `~/.fronius-mcp.json`, so it persists when the server is restarted. The remaining tools query different parts of the installation as needed.

## Setup and configuration

The documented setup targets Claude Desktop and uses `uvx` to run the package without a permanent installation. Install `uv`, add a `fronius` entry under `mcpServers` in Claude Desktop's configuration, and restart Claude Desktop. The configured command is `uvx` with `fronius-mcp` as its argument.

The inverter must be reachable on the local network and have its Solar API, also called the JSON API, enabled. In a new conversation, provide the inverter's IP address through the configuration tool. If the address is unknown, the project documentation suggests finding it through the router, Fronius Solar.web, or the inverter's touch display, and checking the inverter web interface for API enablement.

## Tools and capabilities

- `configure_inverter`: Saves the inverter IP address for later requests.
- `solar_power_flow`: Reports PV output, grid exchange, house load, battery power, autonomy, and energy totals.
- `solar_meter`: Returns per-phase grid power, cumulative import and export energy, voltage, current, and frequency.
- `solar_battery`: Reports battery charge level, electrical readings, temperature, capacity, and status.
- `solar_devices`: Lists connected devices with their type, bus index, and serial number.

## Limitations and notes

The project was developed and tested with a Fronius Symo GEN24 10.0 Plus, a BYD Battery-Box Premium HV battery, and a three-phase Fronius Smart Meter at the grid feed-in point. Other Fronius inverters supporting Solar API v1 may work, but the documentation notes that API endpoints can differ between models.

This server depends on local network access to the inverter and on the Solar API being enabled. If a particular endpoint behaves differently on the installed hardware, the project recommends reporting the issue to its repository.

_Full upstream README: https://allmcps.com/mcp/fronius-mcp/readme_