MCP

What is the Samsara MCP?

The Samsara MCP server connects AI assistants and agents directly to your Samsara data using the Model Context Protocol (MCP) — the open standard that tools like Claude use to talk to external systems.

Once connected, you can ask questions about your fleet in plain language and get answers grounded in your live Samsara data — no copy-paste, no exports, no context switching:

• "Which drivers have hours of service remaining right now?"
• "List yesterday's inspection reports with unresolved defects so I can create work orders."
• "Before tomorrow's crew move, which trucks are below a quarter tank of fuel?"

Because MCP is a standard, the same connection works whether your team lives in Claude, Cursor, an enterprise Copilot agent, or an agent framework you build yourself. Samsara becomes one connector among the tools your team already uses — alongside your TMS, maintenance system, or data warehouse — so agents can blend Samsara data with the rest of your operation.

How it works

Sign in with your Samsara login. The Samsara MCP server uses OAuth: the first time your AI client connects, it opens a browser window where you sign in with your Samsara credentials.

Your access always matches your dashboard permissions. The MCP server enforces the same identity, role, and tag scoping as the Samsara dashboard. An agent acting on your behalf can only see the data you can see. Admins see admin-level data; a user scoped to one tag sees only that tag.

Read-only. Samsara MCP can answer questions about your data but cannot change anything in your Samsara account — no settings changes, messages, or assignments.

Your data stays yours. The MCP server exposes your organization's own operational data, the same data you see in the dashboard.

Availability

Samsara MCP is generally available for supported Samsara organizations:

• The tool surface is read-only (see the Tools Reference).
• Tool names and capabilities may evolve — reconnect your client periodically to pick up changes.
• If you hit an issue, share the full conversation transcript (your prompts plus the tool calls the agent made) with your Samsara contact or in a support ticket. That is the fastest path to a diagnosis, because the agent runs in your AI client, not on Samsara's side.

Connect your client

Match the MCP URL to the dashboard you log into.

Cursor

Add the server to .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global). Swap in your region's URL from the table above:

{
  "mcpServers": {
    "samsara": {
      "url": "https://mcp.samsara.com/v2/mcp"
    }
  }
}

Cursor will prompt you to sign in with your Samsara login the first time the server is used.

Claude Desktop

The organization owner for Claude can make the MCP available for all users by adding it as a custom connector (Settings → Connectors → Add custom connector). Use your region's URL from the table above. Once added, any user can search for the MCP under Settings → Connectors.

Detailed instructions here.

Other MCP clients

Any client that supports remote MCP servers with OAuth sign-in can connect using the MCP endpoint URL from the table above. Setup details vary by client.

What you can ask

The GA tool surface covers fleet and asset visibility, trailer pools, driver and safety data, compliance (hours of service and DVIRs), routes, dispatch, fuel, and locations. See the Samsara MCP — Tools Reference for every tool with example prompts.

FAQ

Can the agent change anything in my Samsara account?
No. Samsara MCP is read-only.

Who in my org can use it?
Users in supported Samsara organizations can sign in individually. Their access mirrors their dashboard permissions.

Which URL should I use?
Match the MCP endpoint to your dashboard region (see the table under Connect your client). A US-cloud org cannot authenticate against the EU or CA endpoint, and vice versa.

Does this replace the Samsara API?
No. The REST API remains the right tool for building integrations and moving data at volume. MCP is for conversational and agent-driven workflows.