The Samsara MCP server connects AI assistants and agents to your Samsara data using the Model Context Protocol (MCP), an open standard that tools such as Claude use to talk to external systems. When you connect a supported client, you can ask questions about your fleet in plain language and get answers grounded in your live Samsara data—without copy-paste, exports, or switching between tools.
The same connection works across Claude, Cursor, enterprise Copilot agents, and agent frameworks you build yourself. The MCP server is read-only: it can answer questions about your data but cannot change settings, send messages, or make assignments in your Samsara account. MCP does not replace the Samsara REST API, which remains the right path for integrations and high-volume data movement. MCP is for conversational and agent-driven workflows.
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.
Access matches your identity, role, and tag scope in the Samsara dashboard. An agent acting on your behalf can see only the data you can see. Admins see admin-level data; a user scoped to one tag sees only that tag.
Anyone with a Samsara dashboard login can use the MCP server. Each user signs in individually. The MCP server exposes your organization's own operational data—the same data you see in the dashboard.
Note
If you hit an issue, share the full conversation transcript (your prompts plus the tool calls the agent made) with your Samsara contact or as a support ticket. The agent runs in your AI client, not on Samsara's side, so the transcript is the fastest path to a diagnosis.
Use the MCP URL that matches your Samsara dashboard region. Your client prompts you to sign in with your Samsara login on first connect.
|
Region |
Dashboard |
MCP Endpoint |
|---|---|---|
|
United States |
|
|
|
Europe / UK |
|
|
|
Canada |
|
|
Match the MCP URL to the dashboard you log into. Some Canadian customers still on US cloud (cloud.samsara.com) should use the US endpoint. If your organization has orgs in more than one region, add the MCP server once per region.
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 prompts you to sign in with your Samsara login the first time the server is used.
-
Add the server:
claude mcp add --transport http samsara https://mcp.samsara.com/v2/mcp
Use
https://mcp.eu.samsara.com/v2/mcporhttps://mcp.ca.samsara.com/v2/mcpif that is your region. -
Run
/mcpinside Claude Code to authenticate and to refresh the tool list after updates.
The organization owner for Claude can make the MCP available for all users by adding it as a custom connector. Use your region's URL from the table above.
-
In Claude, open Settings > Connectors > Add custom connector.
-
Add the Samsara MCP endpoint. After it is added, any user can search for the MCP under Settings > Connectors.
For detailed Claude instructions, see Get started with custom connectors using remote MCP.
The tool surface covers fleet and asset visibility, trailer pools, driver and safety data, compliance (hours of service and DVIRs), and locations. Examples of questions you can ask:
-
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?
For every tool with example prompts, see the Samsara MCP — Tools Reference.
Comments
0 comments
Article is closed for comments.