Skip to main content
Glama
zevocorp

ZEVO Host MCP Server

Official
by zevocorp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZEVO_API_KEYYesYour Client API key (sent as x-api-key)
ZEVO_API_BASE_URLNoOverride for staging/localhttps://api.zevo.io/client-api/v1

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_meA

Get the authenticated ZEVO account (the owner of the API key) and its wallet. Returns user (basic profile) and wallet (id, userId, balance, timestamps). Call this first to confirm which account the integration is acting on behalf of.

list_vehiclesA

List vehicles available to the API key account. Each vehicle carries identity and listing details for a specific Tesla (VIN, location, charge percentage, listing status, registration fields, timestamps). Use the vehicle id or VIN to connect bookings and transactions back to a physical car. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

list_bookingsA

List bookings (rental/trip records) for the API key account. A booking connects a user to a vehicle for a period of time: status, VIN, pricing context, odometer fields, trip timing, related user/vehicle ids, timestamps. Best object for 'who had which vehicle, and when?'. Statuses: pending, cancelled, pre_trip, in_progress, in_termination, repossession, post_trip, vehicle_returned, payment_failed, paid. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

list_active_bookingsA

List only ACTIVE bookings for the API key account — status pre_trip, in_progress, or in_termination (a renter currently has access to the vehicle). Use this to answer 'which vehicles are out on a trip right now?'. Same response shape as list_bookings. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

list_inspectionsA

List inspections (a vehicle's condition captured at a point in a booking, e.g. pre-trip or post-trip walkaround) for the API key account. Includes related user/vehicle/booking ids, inspection type, status, damage-reported flag, damage tags, odometer, trip timing, photos, timestamps. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

list_receiptsA

List receipts (itemized charges ZEVO billed the renter, connected to a booking and vehicle) for the API key account. Amounts are in CENTS and can be negative for refunds. Includes line items, totals, date/timezone, status, base fare paid, platform fee %, and ids. Line item tags: base_fare, platform_fee, toll, supercharger_invoice, supercharger_invoice_surcharge, incidentals, deposit, commission, revenue_share, wallet_deposit, wallet_withdrawal. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

get_receipts_by_vehicleA

List receipts for a specific vehicle available to the API key account. Same shape as list_receipts. Amounts are in cents. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

get_receipts_by_bookingA

List receipts for a specific booking available to the API key account. Same shape as list_receipts. Amounts are in cents. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

list_transactionsA

List wallet ledger transactions for the API key account — money moving into/out of/through a ZEVO wallet. The best endpoint for account statements, wallet history, and payout reconciliation. Fields: amount, description, kind (adding funds, cashing out, booking wallet credit, wallet receipt payment, ...), status (pending/paid/cancelled), lineItems, bookingId, vehicleId, paidAt. Note: receipts record what was CHARGED; transactions record money MOVING in a wallet. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

get_transactions_by_vinA

List wallet transactions for one specific authorized vehicle by VIN. Useful for reconciling the financial activity of a single Tesla across bookings, tolls, supercharging, incidentals, and related wallet movements. Same shape as list_transactions. Returns up to 10 records per page; increase skip by 10 to fetch the next page.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action: active bookings, inspections, account info, vehicles, all bookings, receipts by booking, all receipts, receipts by vehicle, wallet transactions, and transactions by VIN. Overlapping tools like list_active_bookings vs list_bookings are clearly differentiated by status and purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: list_* for collection queries and get_* for specific lookups. The naming is predictable and uniform, with no mixed conventions or ambiguous verbs.

Tool Count5/5

With 10 tools, the server is well-scoped for a host management API. Each tool covers a distinct aspect of the domain (vehicles, bookings, receipts, transactions, account), and the count is within the ideal range without redundancy.

Completeness4/5

The tool set covers the primary read-only workflows: viewing account info, vehicles, bookings, inspections, receipts, and transactions. It lacks write operations (e.g., create or update booking) and a direct get-booking-by-id, but for a read-focused host integration, the surface is largely complete with only minor gaps.

Maintenance

ActivityStale
ResponsivenessNo issues