Skip to main content
Glama
huber

Fronius MCP Server

by huber

Related Servers

Alternatives to Fronius MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive access to Tigo Energy solar system data and analytics. It enables AI assistants to interact with your Tigo solar monitoring system to retrieve production data, performance metrics, system health information, and maintenance insights.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables natural language interaction with the MeteoControl VCOM API v2 for monitoring solar array installations. It allows users to retrieve real-time and historical energy data, system alerts, and detailed asset configuration metrics.
      4
      Apache 2.0
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that connects to Felicity Solar cloud battery data, allowing natural language queries about battery status, cell voltages, and charge state.
      17
      321 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues