Skip to main content
Glama
RicardoSantos

mcp-fsolar

by RicardoSantos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-fsolar

No user-submitted related servers found.

    Related Servers

    • EG4 MCP Server

      matt-dreyer
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for EG4 solar inverters, enabling real-time monitoring, performance analysis, battery health, alerts, maintenance insights, and historical data via natural language.
      MIT

    • Solplanet MCP

      kalmma
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Solplanet ASW5-T inverter, enabling natural language queries about solar energy system status and control.
      MIT

    • foxess-mcp-server

      holger1411
      A
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that enables AI assistants like Claude to access, analyze, and optimize solar energy data from FoxESS inverters.
      3
      MIT

    • Victron VRM MCP Server

      gimi-q
      A
      license
      B
      quality
      D
      maintenance
      Read-only MCP server integrating with the Victron VRM API to monitor solar systems, batteries, alarms, and more.
      41
      9 npm
      6
      MIT

    • MeteoControl MCP Server

      nielsvbrecht
      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

    • mcp-venus-os

      4alvit
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Victron Venus OS that enables reading battery, PV, grid, and inverter data via D-Bus and MQTT, and safely controlling inverter mode and charge limits.
      11
      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

    A3.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct scopes: fleet vs battery vs cell-level, raw vs statistics, health vs history. However, get_health, get_module_health, get_cell_stats, get_cell_voltages, and get_balance_trend all touch on cell/module health and could be confusing without careful reading, though descriptions clarify granularity.

    Naming Consistency5/5

    All tool names follow a consistent get_ + noun pattern, using snake_case for compound names. There are no mixed conventions or vague verbs, making the naming predictable and uniform.

    Tool Count3/5

    With 17 tools, the server sits in the 16–25 range, feeling somewhat heavy for a monitoring API. While each tool serves a specific data need, the count could be trimmed by merging closely related health/cell tools without losing functionality.

    Completeness4/5

    The read-only monitoring surface is fairly complete: live status, health, alerts, energy history, capacity estimates, power stats, cost savings, and lifetime data are all covered. Minor gaps include lack of a dedicated temperature history or per-module raw voltage detail, but these are workarounds via snapshots.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources