evaconnect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVOLUTE_CAR_ID | No | Vehicle ID (car ID) for the Evolute API. Use when not providing a credentials file, or to fill a missing field in the file. | |
| EVOLUTE_CREDENTIALS | No | Path to a credentials.json file containing accessToken, refreshToken, and carId. Overrides the default credentials.json path. | |
| EVOLUTE_ACCESS_TOKEN | No | Access token for the Evolute API. Use when not providing a credentials file, or to fill a missing field in the file. | |
| EVOLUTE_REFRESH_TOKEN | No | Refresh token for the Evolute API. Use when not providing a credentials file, or to fill a missing field in the file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evolute_statusB | Telemetry of the default (or given) vehicle: charge, climate, doors, online. Coordinates are hidden unless include_pii is true. |
| evolute_vehiclesA | List vehicles. VIN/IMEI are masked unless include_pii is true. |
| evolute_tripsB | Recent trips for the default (or given) vehicle. Addresses and track are omitted. Distance is a raw integer (units unknown). |
| evolute_tripC | One trip. Track points only if include_track=true. Addresses only if include_pii=true. start_time is segmentStartTime. |
| evolute_chargeA | Current charge session, if any. Empty when not charging. |
| evolute_auth_statusA | Whether a session looks valid. Never returns raw tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.