evaconnect-mcp
Related Servers
Alternatives to evaconnect-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables read-only access to BMW CarData for vehicle maintenance, tire pressure, and 12V battery status, with caching and local history to stay within the daily API quota.1215 PyPIMIT
- AlicenseAqualityCmaintenanceProvides 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.12MIT
- AlicenseAqualityDmaintenanceProvides 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.10MIT
- AlicenseAqualityAmaintenanceEnables 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.994 npm4MIT
- AlicenseAqualityAmaintenanceEnables users to query a Tesla vehicle's battery, charging, climate, odometer, software, location, charging history, and local mileage or range reports through a local stdio MCP connector. Status can come from cached snapshots without waking the car, while wake-and-refresh is budget-gated and no vehicle commands are exposed.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only, self-hosted access to official EVE Online SSO/ESI data for multiple independently authorized characters, covering character status, skills, assets, mining ledger, industry jobs, blueprints, wallet transactions, and market orders. It includes source character, data freshness, counts, and truncation metadata without interacting with the EVE client.MIT
TDQS
Scored across 6 tools
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.
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.
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.
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.