Skip to main content
Glama
4alvit

mcp-venus-os

by 4alvit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-venus-os

No user-submitted related servers found.

    Related Servers

    • 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

    • mcp-fsolar

      RicardoSantos
      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
      146 npm
      MIT

    • victron-tcp

      lubosstrejcek
      A
      license
      A
      quality
      A
      maintenance
      Connect AI assistants to Victron Energy systems to read real-time solar, battery, grid, and inverter data from your local network via Modbus TCP or MQTT.
      32
      13 npm
      3
      MIT

    • shelly-mcp

      Buggy1111
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.
      2
      47
      38 PyPI
      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
    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 11 tools

    Disambiguation5/5

    Each tool targets a distinct device metric, setting, or MQTT lifecycle action. Read, write, and connection verbs create clear boundaries, and no two tools appear to perform the same operation.

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern: get_* for reads, set_* for writes, and mqtt_* for connection controls. list_devices is the only slight deviation but remains conventional and predictable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a Victron monitoring and control interface. The count is substantial enough to cover core operations without feeling bloated or redundant.

    Completeness3/5

    The main monitoring and control surface is solid, but there is no direct load/consumption tool, which is a notable gap for energy management. Additionally, mqtt_subscribe is explicitly unimplemented, creating a dead end for real-time streaming workflows.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources