Samsara MCP connector
The Samsara connector brings your fleet's assets, addresses, alerts, attributes, and live location and speed streams into Claude, ChatGPT, Cursor, and the Elaichi Agent, with every request running inside the signed-in person's own Samsara access.
-
How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Samsara to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Samsara once
-
Open Connections, choose Add connection, and pick Samsara.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Samsara app, then approve. Samsara needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Samsara MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Samsara MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Samsara MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Samsara to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Samsara through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Dispatch
Add a new customer site as an address
When a shipper sends over a new yard or dock, add it to Samsara as an address from the chat, then check it back later to confirm the details stuck.
-
Operations
Find out where an asset is right now
Ask for the latest location and speed of a trailer or a piece of equipment and get the answer from Samsara's live stream instead of scrolling a map.
-
Safety
Review the week's incidents in one pass
Pull the incidents stream for the last seven days and get it summarized by site or by asset so the Monday safety call starts with the facts.
-
Fleet maintenance
Keep asset attributes consistent across the fleet
List the attributes on your assets, spot the ones with missing or outdated tags, and update or create attributes in bulk so crews can find what they need.
-
Finance
Pull asset depreciation figures for the quarter
Ask for the depreciation records on your Samsara assets and have them grouped by category, ready to paste into the quarter-end workbook.
-
Operations
Tidy alert configurations across the organization
List every alert configuration in Samsara, find the duplicates and the stale ones, and update or remove them in bulk from a single conversation.
Try asking
- “Where is trailer 4471 right now and how fast is it moving?”
- “Summarize last week's incidents by site”
- “Add the new Dallas cross-dock as an address”
Compare
Elaichi vs Zapier MCP vs Composio for Samsara
All three can connect Samsara to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Samsara tools | Allow or restrict single Samsara tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Samsara call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Samsara tools for your AI agents
343 tools are ready to call through Elaichi's MCP endpoint the moment you connect Samsara, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 277 of 343 Samsara tools here. Connect Samsara and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Samsara gets you
6 screens from the product, each doing one job for your Samsara account.
The agent
Ask about your fleet in plain language.
Get answers from live Samsara assets, addresses, and alerts without opening a dashboard.
- assets
- addresses
- alerts
- attributes
Ask Elaichi to work across your apps.
Where is trailer 4471 right now and how fast is it moving?
Summarize last week's incidents by site
Add the new Dallas cross-dock as an address
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Samsara from any client.
Claude, ChatGPT, and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
343 Samsara tools, ready without code.
Assets, addresses, alerts, attributes, and streams are covered, with nothing to build.
- List all Samsara addresses
- Create a Samsara address
- Get single Samsara address by ID
- Update a Samsara address by ID
Toolboxes
Every team gets its own Samsara toolbox.
Dispatch, safety, and finance each work from a toolbox scoped to their job.
- Dispatch
- Operations
- Safety
- Fleet maintenance
Shared connections
Teammates use Samsara without seeing a credential.
One person connects, shares with teams, and the client secret stays out of sight.
- Dispatch
- Safety
- Operations North
- Operations South
Audit log
Every Samsara call is recorded and attributed.
See who changed an asset or alert, when, and from which client.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Samsara work on its own.
Incidents are fetched, grouped, and drafted into a digest a person approves before posting.
Samsara digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch assets
Samsara
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Samsara
Queued
Collections and dashboards
Samsara fleet health, computed on a schedule.
Four metrics, a 14 day chart, and a team breakdown, with no model in the math.
Samsara health
Refreshed 4 minutes ago · every 15 minutes · from the assets collection
Assets
1,284 ↓ 12%
Addresses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Assets created
Last 14 days
By team
Share of activity
Dispatch 34%
Safety 27%
Operations North 21%
Operations South 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Samsara to Claude?
Connect Samsara in Elaichi first: Samsara needs an OAuth application registered inside your own Samsara account, so someone brings that client ID and secret once, or pastes a Samsara API key instead. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and your Samsara assets, addresses, and alerts are available in the chat.
Does Samsara work with ChatGPT and Cursor as well as Claude?
Yes. Once Samsara is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Samsara once and every client uses that one connection.
What can an AI agent actually do with my Samsara data?
An agent can look up, add, update, and remove Samsara addresses and assets, read live location and speed streams, review incidents, and manage alert configurations and attributes, including bulk changes. It can also pull asset depreciation records and list voice sessions. Short, concrete asks work best, such as asking where a specific trailer is or for last week's incidents at one site.
Does connecting Samsara give the AI access to my whole fleet?
No. Every call to Samsara runs as the person who signed in, so the AI sees only the assets, addresses, and alerts that person can already see in Samsara. Elaichi can narrow that access further for a team or a role, but it can never widen it beyond what Samsara itself allows.
Can I stop an agent from deleting or changing things in Samsara?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Samsara assets and addresses while blocking deletes or bulk updates. A restricted action is left out of the tool list the AI client receives, so it cannot be called no matter what the prompt says.
What happens to a Samsara connection when someone leaves?
Offboarding that person in Elaichi ends their access to Samsara through every client at once. A Samsara connection shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Samsara once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the Samsara MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Samsara is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Samsara?
Yes. Both let Claude, ChatGPT or Cursor use Samsara. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Samsara call.
How is Elaichi different from Composio for Samsara?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Samsara: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Samsara in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.