# Tesla Fleet API MCP

> Tesla Fleet API allows your agent to remotely control physical hardware on active Tesla vehicles. Check GPS locations, monitor battery health, manage door locks, or trigger lights and horns across an entire fleet—all through a secure, programmatic interface.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** telemetry, hardware-actuation, fleet-operations, gps-tracking, battery-monitoring, remote-control

## Description

Managing a large vehicle fleet means more than just tracking data; it requires physical interaction with the cars themselves. This MCP lets you run commands that actuate real-world hardware on Tesla vehicles. You can pull live telemetry like GPS coordinates and battery state of charge (SoC), or you might need to manually trigger a relay, such as opening the charging port or locking all doors remotely. The system handles complex requirements, including knowing when a vehicle is asleep and needing to wake it up first before any command will work. By connecting this MCP via Vinkius, your AI client gains direct, programmatic control over core operational functions, making physical fleet management automated.

## Tools

### tesla_control_charge_port
Remotely activates the charging port relay after safely waking up the vehicle.

### tesla_control_doors
Controls the physical locks, allowing you to secure or unlock the doors of a vehicle.

### tesla_flash_lights
Triggers external headlights by flashing them after waking up the car.

### tesla_get_vehicle_data
Pulls key telemetry data, including battery SoC, GPS coordinates, and internal temperatures, only after waking the vehicle first.

### tesla_honk_horn
Remotely activates the physical horn mechanism to sound a loud alert after waking up the car.

### tesla_list_vehicles
Retrieves a list of all vehicles in the fleet that are currently tracked by the system.

### tesla_trigger_climate
Engages the internal climate control system to set temperature states before arrival, after triggering wake-up.

### tesla_wake_up_vehicle
The critical first step: triggers the vehicle's ignition sequence to pull it out of an idle sleep state.

## Prompt Examples

**Prompt:** 
```
Check active fleet execution tracking natively extracting explicitly the battery SoC of vehicle XYZ safely resolving sleep delays initially.
```

**Response:** 
```
Parsed logically evaluating native wake sequences (`wake_up_vehicle`) avoiding timeouts implicitly. After latency bounds resolved cleanly, (`get_vehicle_data`) extracted telemetry cleanly outputting 65% battery level appropriately safely routing inherently.
```

**Prompt:** 
```
Actuate physical lock boundaries explicitly mapping the endpoints locking the doors inherently securely natively targeting 'car-aabbcc' dynamically.
```

**Response:** 
```
Logical validation executed cleanly bounding constraints passing seamlessly checking actively wake states safely smoothly bounding locking explicit native parameters. (`control_doors`). Commands received explicitly locking.
```

**Prompt:** 
```
Sound the explicit vehicle horn targeting proxy array bounds locating physical target effectively resolving native bounds gracefully mapping targets.
```

**Response:** 
```
Validating native API timeouts smoothly tracking cleanly isolating `honk_horn` correctly asserting constraints parsing actively safely formatting physical responses perfectly cleanly.
```

## Capabilities

### Monitor Vehicle Status
Get live data on battery charge (SoC), mileage, GPS location, and internal temperatures for specific vehicles.

### Actuate Physical Locks
Send commands to remotely lock or unlock the doors of a vehicle.

### Wake Vehicles from Sleep
Safely wake up vehicles that are in an idle, sleeping state so subsequent commands will execute successfully.

### Control External Systems
Remotely trigger physical elements like the horn, headlights, or charging port relays.

## Use Cases

### Prepping an arrival location
A logistics worker is due in 30 minutes. Instead of driving up and having to manually open doors or adjust the air conditioning, your agent first calls `tesla_wake_up_vehicle`. Then, it uses `tesla_trigger_climate` and `tesla_control_doors` to ensure the car is warm and accessible when they arrive.

### Emergency location tracking
A fleet manager needs to know if a vehicle left its designated parking zone. The agent first runs `tesla_wake_up_vehicle`, then calls `tesla_get_vehicle_data` repeatedly until the GPS coordinates confirm it's back within range.

### Confirming security status
Before leaving a site, an operator needs to ensure all cars are locked down. The agent first runs `tesla_list_vehicles` to see what's available, then loops through and calls `tesla_control_doors` on each one to confirm they are secured.

### Remote vehicle signaling
A parked car needs attention. The agent first runs `tesla_wake_up_vehicle`, then triggers a sequence of physical warnings by calling both `tesla_honk_horn` and `tesla_flash_lights` to draw immediate attention.

## Benefits

- The `tesla_get_vehicle_data` tool lets you get instant access to critical metrics like SoC, odometer reading, and exact GPS coordinates without needing physical proximity.
- Never guess if a car is locked up. Use `tesla_control_doors` to remotely verify the status of vehicle locks or change them instantly from your agent.
- `tesla_wake_up_vehicle` handles the critical first step: it forces the vehicle out of sleep mode, which allows all subsequent commands—like those for lights or climate control—to work reliably.
- You can use `tesla_trigger_climate` to adjust internal temperatures before personnel arrive, making the car comfortable immediately upon arrival. This saves time and effort.
- For simple alerts or locating a vehicle, running `tesla_honk_horn` or `tesla_flash_lights` acts as a reliable, remote attention-grabbing mechanism for the entire fleet.

## How It Works

The bottom line is: it provides reliable, multi-step control over vehicle electronics and relays, respecting the car's sleep cycle to prevent errors.

1. First, your agent must call `tesla_wake_up_vehicle` to ensure the vehicle is online and ready to accept commands.
2. Next, after waiting 10-15 seconds for the system to stabilize, you can execute specific actions like fetching data using `tesla_get_vehicle_data` or triggering a physical relay.
3. The agent receives real-time status updates or confirmation that the hardware command (like locking doors) was successfully sent.

## Frequently Asked Questions

**How do I use tesla_get_vehicle_data reliably?**
You must always run `tesla_wake_up_vehicle` first, then wait 10-15 seconds. Only after that sequence completes should you call `tesla_get_vehicle_data` to pull the actual telemetry data.

**Can I use tesla_control_doors before waking up the vehicle?**
No. The API will fail if the car is sleeping. You must always start with `tesla_wake_up_vehicle` to ensure the physical relays can be accessed and manipulated.

**Which tool shows me all cars in my fleet?**
`tesla_list_vehicles` provides a comprehensive list of every vehicle ID currently tracked by the system. You use this first if you need to run an action on multiple units.

**What happens if I forget to wait after waking up the car?**
If you don't wait, your agent will likely encounter a timeout error (HTTP 408) because the system needs time to transition from sleep mode back into full operational status.

**Can I check battery SoC and GPS at the same time with tesla_get_vehicle_data?**
Yes, `tesla_get_vehicle_data` pulls a master telemetry package that includes both the current State of Charge (SoC) percentage and the precise GPS coordinates in one call.