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 with your Samsara contact or in a support ticket.

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.

ChatGPT Enterprise

ChatGPT Enterprise administrators and owners can create a custom app backed by Samsara MCP. OpenAI is moving from the Plugins label to Apps, so your workspace can show either label.

Before you begin:

• A ChatGPT Enterprise administrator or owner must allow custom MCP apps through the workspace's developer-mode and connected-data permissions.
• The administrator must grant the intended role access to create or use custom MCP apps.
• Choose the regional Samsara MCP endpoint that matches your dashboard.

1. In the ChatGPT Admin Console, open Workspace settings.
2. Under Permissions & Roles, enable Developer mode / Create custom MCP connectors for the administrators or roles that will configure Samsara MCP.
3. Open Apps or Plugins, then select Add and Add custom MCP server.
4. Enter the app details:
   • Custom name: Use a recognizable name that includes the region, such as Samsara MCP US.
   • Description: Explain that the app provides read-only access to authorized Samsara fleet data.
   • Connection: Select Server URL.
   • Server URL: Paste the regional endpoint from the table above.
   • Authentication: Select OAuth.
5. Review the warning for custom MCP apps, then create the draft app.
6. Complete the Samsara browser sign-in and authorization flow. Each person connects with their own Samsara account.
7. Review the discovered read tools and continue.
8. From the workspace's Apps or Plugins settings, publish or enable the app for the intended roles. Enterprise apps are disabled by default until an administrator enables access.
9. Open the app, connect an authorized Samsara account, and select Try now or start a new ChatGPT conversation with the app enabled.

For OpenAI's current interface and requirements, see Developer mode and MCP apps in ChatGPT and Add custom MCP server.

If authorization expires or tools do not load, reconnect the app and complete OAuth again. If the problem continues, record the ChatGPT workspace, regional MCP endpoint, timestamp, and displayed error for Samsara Support.

Microsoft Copilot Studio

You can add Samsara MCP to an agent in Microsoft Copilot Studio by using OAuth 2.0 dynamic discovery. Before you start, create or open an agent in Copilot Studio and choose the regional Samsara MCP endpoint that matches your dashboard.

1. Open your agent in Microsoft Copilot Studio.
2. On the Build tab, select Tools, then select Add a tool.
3. Select Add, then select Model Context Protocol (MCP).
4. Enter the MCP server details:
   • Server name: Use a recognizable name that includes the region, such as Samsara US.
   • Server description: Describe when the agent should use Samsara data.
   • Server URL: Paste the regional endpoint from the table above.
   • Authentication: Select OAuth 2.0.
   • Configuration type: Select Dynamic (with discovery).
5. Continue to Select a connection, then create a new connection.
6. Complete the Samsara browser sign-in and authorization flow. If Samsara asks an eligible administrator to Approve connector, review the read-only permission and approve it for the organization. Each user still authorizes access with their own Samsara account.
7. Return to Copilot Studio, select the connected Samsara account, and add the MCP server to the agent.
8. Open Preview and ask a question that uses Samsara data to confirm the connection.

For Microsoft's current interface and requirements, see Connect your agent to an existing MCP server.

If you change the MCP endpoint, authentication configuration, or available tools, edit the server under Tools to refresh the connection and tool list.

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. 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.