Samsara MCP server

What the model can do

Samsara fleet operations: vehicles and their assigned drivers, drivers by name, trips by vehicle (times and distance, never locations), hours-of-service violation summaries per driver, DVIRs and their defects, issues, dispatch routes and maintenance work orders. Can create, update, cancel or delete work orders, resolve defects, open and update issues, record and resolve mechanic DVIRs, create, change or delete routes, and deactivate or reactivate a driver.

Reads

• samsara_list_vehiclesVehicles in Samsara: name, make, model, year, VIN, licence plate, assigned driver's name and tags.
• samsara_list_driversDrivers in Samsara by name and id, with activation status and tags.
• samsara_list_tripsTrips for up to 50 vehicles or assets in a window (default the last 7 days, at most 31): start and end time, status…
• samsara_hos_violationsHours-of-service violations in a window (default the last 7 days, at most 31), summarised per driver: how many, which kinds and hours in violation.
• samsara_list_defectsDVIR defects changed in a window (default the last 14 days, at most 90): vehicle or trailer, the driver's comment, safe or unsafe…
• samsara_list_work_ordersMaintenance work orders changed in a window (default the last 30 days, at most 90): asset id, status, priority, category, description, due…
• samsara_list_issuesIssues raised against vehicles, trailers and equipment that changed in a window (default the last 30 days, at most 90): title, status, priority…
• samsara_list_dvirsDriver vehicle inspection reports (DVIRs) that changed in a window (default the last 14 days, at most 90): vehicle or trailer, safe or unsafe…
• samsara_list_routesDispatch routes scheduled in a window (default the next 7 days from today, at most 31): name, driver and vehicle by name…

Acts, when you ask

These change something in Samsara. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• samsara_create_work_orderCreates a maintenance work order in Samsara for one vehicle or asset, with Samsara's default status (Open), as the API token.
• samsara_update_work_orderChanges a Samsara maintenance work order (id from samsara_list_work_orders): status (not Cancelled: use samsara_cancel_work_order), priority…
• samsara_cancel_work_orderCancels a Samsara maintenance work order (sets its status to Cancelled, which Samsara also archives), with optional closing notes.
• samsara_delete_work_orderPermanently deletes a Samsara maintenance work order and its history.
• samsara_resolve_defectMarks a DVIR defect (id from samsara_list_defects) resolved, with the mechanic's notes, and optionally which mechanic…
• samsara_create_issueOpens an issue in Samsara against one vehicle, trailer or piece of equipment (asset id, or key:value external id)…
• samsara_update_issueChanges a Samsara issue (id from samsara_list_issues): status (open, inProgress, resolved, dismissed), priority, title, description…
• samsara_create_dvirRecords a mechanic's DVIR (vehicle inspection report) in Samsara for one vehicle or trailer, signed by the mechanic named…
• samsara_resolve_dvirSigns off and resolves a DVIR in Samsara (id from samsara_list_dvirs), as the mechanic named (a Samsara dashboard user id), with optional notes.
• samsara_set_driver_activeDeactivates a Samsara driver (active false), which removes their driver app access and stops them being assigned, or reactivates them (active true).
• samsara_create_routeCreates a dispatch route in Samsara with its stops, optionally for a driver and vehicle.
• samsara_update_routeChanges a Samsara dispatch route's name, notes, driver or vehicle (id from samsara_list_routes).
• samsara_delete_routePermanently deletes a Samsara dispatch route and its stops; its driver loses it from the driver app.

Connect it

First connect Samsara on Dashboard → Connections, then add Memtro to your client once. The Samsara tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Samsara connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which vehicles have open unsafe defects?
• › How far did Truck 7 drive last week?
• › Which drivers had hours-of-service violations this week?
• › Which work orders are still open?
• › Create a work order to replace the brake light on Van 12.

Questions

Is this an official Samsara MCP server?

No. It is Memtro's MCP server with Memtro's Samsara connector behind it: the connector reads Samsara through its API with the credentials you connect on Dashboard → Connections, and Samsara publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Samsara?

Only when you ask, and only what it has been granted: create a maintenance work order for a vehicle or asset; update a work order's status, priority, description, notes, due date or assigned mechanic; cancel a work order, or delete one permanently; mark a vehicle defect resolved, with mechanic's notes; open an issue against a vehicle, trailer or equipment, or change an issue's status, priority, assignee or due date; record a mechanic's DVIR for a vehicle or trailer, or sign off and resolve a DVIR; create a dispatch route with stops for a driver or vehicle, change its name, notes, driver or vehicle, or delete it; deactivate a driver, removing their driver app access, or reactivate them. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server