Skip to main content
Glama
Sign In
unofficialzaptecMCP

unofficialzaptecMCP

by holger1411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to unofficialzaptecMCP

  • Home Assistant MCP Server

    Home Assistant MCP Serverofficial

    homeassistant-ai
    A
    license
    A
    quality
    A
    maintenance
    A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
    77
    196,503 PyPI
    5,847
    MIT

Related Servers

  • tibber-mcp-server

    Schimmilab
    A
    license
    A
    quality
    B
    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
    27 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.
    6 npm
    MIT

  • bluelink-mcp

    mattoddie
    A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to monitor a Hyundai, Kia, or Genesis vehicle's charge, fuel, range, locks, and location, and optionally pre-heat the cabin, lock or unlock doors, and start or stop charging. Reads come from cached Bluelink data with rate-limited refreshes, and all write commands are disabled by default.
    6
    2
    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

ActivitySlowing
ResponsivenessOutdated data

Resources