Skip to main content
Glama
ca11mebaraka

evaconnect-mcp

by ca11mebaraka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to evaconnect-mcp

No user-submitted related servers found.

    Related Servers

    • garmin-cn-mcp

      love-wizard
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to a China-region Garmin Connect account, enabling retrieval of daily summaries, sleep, heart rate, HRV, training readiness, body battery, and activity data.
      12
      MIT

    • Alpha ESS MCP Server

      michaelkrasa
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Alpha ESS solar inverter and battery system data, enabling monitoring of energy statistics, real-time power data, and configuration of battery charging and discharge schedules through the Alpha ESS Open API.
      10
      MIT

    • Rivian MCP

      PatrickHeneise
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to vehicle data via the unofficial Rivian GraphQL API, allowing users to monitor battery levels, OTA updates, and charging status. It provides tools to check vehicle state and user account information directly through Claude.
      9
      8 npm
      2
      MIT
    • Cariot MCP Server by CariotInc

      Cariot MCP Serverofficial

      CariotInc
      A
      license
      B
      quality
      C
      maintenance
      Enables querying Cariot APIs for fleet management data, including alcohol checks, daily reports, drivers, vehicles, and realtime snapshots, with utility for generating chart configurations.
      7
      28 npm
      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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct: vehicles, trips, trip, auth_status, and charge each target a separate resource. The only mild overlap is evolute_status including charge information while evolute_charge focuses on the active charging session, but the descriptions clarify the boundary.

    Naming Consistency5/5

    All tools follow the same evolute_ noun pattern with snake_case. Singular/plural is used intuitively (trips vs trip), and the naming is predictable across the entire set.

    Tool Count5/5

    Six tools is a well-scoped count for an EV telemetry and connectivity server. Each tool covers a meaningful read-only operation without unnecessary bloat.

    Completeness4/5

    The tool set covers the core read-only domain: vehicle listing, current status, recent trips, trip details, active charge session, and auth validation. Minor gaps exist such as no direct vehicle detail endpoint or historical charge sessions, but the main workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources