Skip to main content
Glama
holger1411

unofficialzaptecMCP

by holger1411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to unofficialzaptecMCP

No user-submitted related servers found.

    Related Servers

    • tibber-mcp-server

      Schimmilab
      A
      license
      A
      quality
      A
      maintenance
      Enables querying Tibber electricity prices, forecasts, consumption data, cheapest hours, and live Pulse measurements through natural language.
      7
      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
      5 npm
      MIT

    • 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.
      3 npm
      MIT

    • homey-mcp

      tim661811
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.
      36
      9 npm
      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.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    get_status and get_installation both expose available current and installation mode, creating minor overlap. However, each tool otherwise targets a distinct aspect (real-time charging state, installation configuration, historical sessions), and pause/resume are clearly opposite actions with explicit validity conditions.

    Naming Consistency5/5

    All tools use the zaptec_ prefix followed by a consistent verb_noun pattern in snake_case (get_status, get_installation, get_charge_history, pause_charging, resume_charging, set_available_current). No deviations or mixed conventions.

    Tool Count5/5

    6 tools cover the core read and control operations for an EV charger, and each tool earns its place with a distinct purpose. The count is well within the ideal 3-15 range for this scope.

    Completeness4/5

    Core monitoring (status, installation, history) and control (pause/resume, set available current) are covered. However, there is no explicit start/stop charging command and no way to set installation-wide mode or phase configuration, representing minor gaps that agents can likely work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources