Fronius MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: error, warn, info, debug | info |
| FRONIUS_HOST | No | Hostname or IP of Fronius device | fronius-inverter |
| FRONIUS_PORT | No | Port | 80 |
| FRONIUS_RETRIES | No | Number of retry attempts | 3 |
| FRONIUS_TIMEOUT | No | Request timeout in ms | 10000 |
| FRONIUS_PROTOCOL | No | Protocol: http or https | http |
| FRONIUS_DEVICE_ID | No | Default device ID | 1 |
| FRONIUS_RETRY_DELAY | No | Delay between retries in ms | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_versionA | Get Fronius Solar API version information |
| get_system_statusB | Get system status and logger information |
| get_logger_led_infoA | Get logger LED status information |
| get_inverter_infoC | Get static inverter information |
| get_inverter_realtimeB | Get real-time inverter data including power, energy, voltage, current |
| get_meter_realtimeB | Get real-time smart meter data |
| get_powerflow_realtimeA | Get real-time power flow data showing energy production, consumption, and grid interaction |
| get_archive_dataB | Get historical archive data for a specific time period |
| get_sensor_realtimeB | Get real-time sensor data (temperature, irradiance, wind, etc.) |
| get_string_realtimeA | Get real-time DC string data (voltage and current per string) |
| get_storage_realtimeA | Get real-time battery storage data (state of charge, power, temperature) |
| get_ohmpilot_realtimeA | Get real-time OhmPilot data (smart heating element controller power and temperature) |
| get_active_devicesC | Get information about active devices in the system |
| test_connectionA | Test the connection to the Fronius device |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| API Version | Fronius Solar API version information |
| System Status | Logger and system information |
| LED Status | Logger LED status information |
| Inverter Information | Static inverter information |
| Inverter Realtime Data | Current inverter measurements and status |
| Smart Meter Realtime Data | Current smart meter measurements |
| Power Flow Realtime Data | Energy flow data showing production, consumption, and grid interaction |
| Sensor Realtime Data | Environmental sensor data (temperature, irradiance, etc.) |
| String Realtime Data | DC string voltage and current measurements |
| Storage Realtime Data | Battery storage system data including state of charge, power, and temperature |
| OhmPilot Realtime Data | Smart heating element controller data including power consumption and temperature |
| Active Devices | List of active devices in the system |
TDQS
Scored across 14 tools
Most tools target distinct sub-systems (inverter, meter, powerflow, sensor, storage, string, ohmpilot), making them easy to tell apart. However, get_system_status and get_logger_led_info overlap in scope, and get_active_devices could cause confusion with resource-specific tools.
The vast majority of tools follow a get_<resource>_<type> pattern, but test_connection breaks this. Additionally, only inverter has both info and realtime variants, while other resource types only have realtime, creating slight inconsistency across devices.
14 tools is a well-scoped size for a Fronius solar monitoring server, covering all major subsystems without being excessive. Each tool serves a specific data access need.
The server provides comprehensive real-time data, historical archive access, and connection testing. However, static info is only available for the inverter, leaving gaps for static information about meter, sensor, storage, and other devices.