ZEVO Host MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZEVO_API_KEY | Yes | Your Client API key (sent as x-api-key) | |
| ZEVO_API_BASE_URL | No | Override for staging/local | https://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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meA | Get the authenticated ZEVO account (the owner of the API key) and its wallet. Returns |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zevocorp/zevo-host-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server