mcp-samsara
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAMSARA_BASE_URL | No | API base URL (use EU endpoint if needed). | https://api.samsara.com |
| SAMSARA_API_TOKEN | Yes | Your Samsara API token. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| samsara_list_vehiclesA | List all vehicles in the fleet. Returns vehicle details including ID, name, VIN, make, model, and external IDs for TMS integration. |
| samsara_get_vehicleB | Get detailed information about a specific vehicle by ID |
| samsara_get_vehicle_locationsA | Get real-time or recent locations for vehicles. Uses the feed API pattern for efficient streaming of location data. |
| samsara_get_vehicle_statsB | Get vehicle statistics including odometer, engine hours, and fuel usage over a time range |
| samsara_list_routesA | List all routes. Routes contain ordered stops with addresses, times, and status tracking. |
| samsara_get_routeA | Get detailed information about a specific route including all stops, assigned vehicle/driver, and status |
| samsara_create_routeA | Create a new route with stops. IMPORTANT: Each stop needs address (with lat/long or formatted address), optional arrival/departure times, and names. Use externalIds to link with your TMS. |
| samsara_update_routeA | Update a route. CRITICAL BEST PRACTICE: This tool automatically preserves stop IDs to maintain arrival/departure time tracking. You can update name, vehicle, driver, status, or modify stops. When updating stops, the tool fetches existing stop IDs and preserves them. |
| samsara_delete_routeC | Delete a route permanently |
| samsara_optimize_routeB | Optimize route stop order to minimize distance/time. This is a value-add feature that reorders stops for efficiency while preserving all stop data and IDs. |
| samsara_list_driversC | List all drivers in the organization with their details and external IDs |
| samsara_get_driverC | Get detailed information about a specific driver |
| samsara_get_driver_hosC | Get Hours of Service (HOS) logs for a driver. Essential for compliance tracking. |
| samsara_get_driver_safety_eventsC | Get safety events (harsh braking, acceleration, speeding, etc.) for a driver |
| samsara_create_addressC | Create a saved address/location in Samsara for reuse in routes |
| samsara_list_addressesB | List all saved addresses |
| samsara_create_webhookB | Create a webhook to receive real-time notifications from Samsara (route updates, vehicle events, etc.) |
| samsara_list_webhooksB | List all configured webhooks |
| samsara_delete_webhookC | Delete a webhook subscription |
| samsara_create_contactC | Create a contact (person at a stop location) for route management |
| samsara_list_contactsD | List all contacts |
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 21 tools
Most tools have distinct purposes (vehicles, routes, drivers, addresses, webhooks, contacts). However, samsara_list_vehicles and samsara_get_vehicle could be confused by an agent as simply different granularities of the same resource, which is acceptable. No major overlapping ambiguity.
All tools follow a consistent samsara_{verb}_{noun} pattern with clear CRUD verbs (list, get, create, update, delete) and one value-add verb (optimize). The naming is predictable and uniform, making it easy for an agent to infer tool purpose.
21 tools covers a fleet management domain (vehicles, routes, drivers, HOS, safety, addresses, webhooks, contacts) reasonably well. It is on the higher side but each tool serves a clear function. Slightly over 15 but not excessive for the scope.
The toolset provides good CRUD coverage for routes, addresses, webhooks, and contacts, plus read-only access for vehicles and drivers with HOS and safety. Missing update/delete for drivers and vehicles, and no update for addresses/contacts, but the core fleet workflows (routing, driver monitoring) are well-covered.