Skip to main content
Glama
lubosstrejcek

victron-tcp

by lubosstrejcek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to victron-tcp

No user-submitted related servers found.

    Related Servers

    • Powerline

      EdidiongA
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables conversational home power management by providing real-time solar, battery, and grid status, plus forecasts to answer questions like whether you can run an appliance. It supports Victron and Growatt inverters, remembers household appliances and grid events, and renders an interactive dashboard card in MCP-compatible clients.
      4 npm
      MIT

    • viaris-mcp

      Nolex13
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor and control Orbis Viaris EV chargers over the local network, including live power status, charging schedules, history, and power limits, with no cloud dependency.
      12
      6 npm
      MIT

    • MQTT MCP Server

      eduard256
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to MQTT brokers for smart home automation and IoT device control, enabling topic discovery, sensor reading, command sending, and event monitoring.
      2
      MIT

    • Fronius MCP Server

      huber
      A
      license
      A
      quality
      D
      maintenance
      Enables access to Fronius solar inverter data via the MCP protocol, allowing real-time monitoring of energy production, consumption, and battery storage through natural language.
      14
      20 npm
      4
      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

    A4.1/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool targets a specific Victron device or function (e.g., solar, battery, inverter) with clear, distinct purposes. No two tools have overlapping functionality; even general-purpose tools like victron_read_register are explicitly for advanced use and do not conflict with specific status tools.

    Naming Consistency5/5

    All tools follow a consistent 'victron_<target>_<action>' pattern, where the target is a device (e.g., solar, battery) and the action is typically 'status' or a descriptive noun (e.g., discover, setup). No mixing of naming conventions or irregular verbs.

    Tool Count4/5

    With 32 tools, the set is extensive but justified by the complexity of Victron systems covering many device types (solar, inverters, batteries, etc.). The number feels appropriate for comprehensive monitoring, though slightly above the typical 3-15 range for simpler domains.

    Completeness4/5

    The tool set covers nearly all common Victron device categories for status reading (solar, battery, inverter, grid, generator, etc.), including discovery and search. Missing write/configuration tools, but these are not part of the server's stated scope (reading status).

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources