Skip to main content
Glama
Nolex13

viaris-mcp

by Nolex13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to viaris-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      168 npm
      4
      MIT

    • unofficialzaptecMCP

      holger1411
      A
      license
      A
      quality
      B
      maintenance
      Enables controlling Zaptec EV chargers through natural language, including checking charging status, viewing charge history with cost, pausing and resuming sessions, and setting available current.
      6
      MIT

    • anker-solix-mcp

      gkoenig
      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
    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 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: status, history, configuration, schedules, and separate setters for charging, power limits, solar, LED, and time. The only potentially similar pair, set_home_power_limit and set_charger_current_limit, is clearly differentiated by household supply vs. car charger current.

    Naming Consistency5/5

    The naming follows a consistent verb_noun pattern: get_* for reads, set_* for configuration changes, and add_/remove_ for schedule mutations. All tools use snake_case and the verbs accurately reflect their operations.

    Tool Count5/5

    Twelve tools is well-scoped for an EV charger management server, covering status, history, configuration, scheduling, and control without redundancy. Each tool has a clear purpose and none feel superfluous.

    Completeness5/5

    The set covers the main charger lifecycle: observing status/history/config, managing schedules, and controlling charging, power limits, solar, LED, and time. The lack of a remote-stop tool is explicitly explained as unsupported by the hardware, and configuration changes outside the MCP are clearly scoped to the web interface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources