Logistics
Onfleet MCP connector
Connect Onfleet to Elaichi once and Claude, ChatGPT, Cursor, or any MCP client can create and update delivery tasks, check driver status, and look up recipients inside each person's own Onfleet access.
-
How it connects. Connects with an 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 Onfleet to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Onfleet once
-
Open Connections, choose Add connection, and pick Onfleet.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Onfleet API key. One person generates a token in Onfleet and pastes it once. Everyone else works through Share with, and never sees it.
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.
Onfleet 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.
Onfleet 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.
Onfleet 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 Onfleet 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 Onfleet through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Dispatch
Create today's delivery tasks in one go
Paste the day's orders and have each one created in Onfleet with its destination and recipient, then auto-assigned to the drivers who are on shift.
-
Support
Find a delivery from a phone number
When a customer calls, look up the recipient by phone, pull up their task, and tell them where the delivery stands and who is bringing it.
-
Operations
Reschedule a route when plans change
Update a task's time window and notes, clone a recurring pickup for tomorrow, or mark a task complete after a driver confirms by phone.
-
Fleet
Onboard a new driver before their shift
Create the worker in Onfleet, put them on the right team, and correct their phone or vehicle details without opening the dashboard.
-
Warehouse
Check whether the bulk upload finished
After importing hundreds of tasks, ask for the batch status and find out which tasks were created and which ones need a fix.
-
Account management
Answer a client's question about their deliveries
List the tasks for a client's deliveries and summarize what was completed, what is still pending, and which drivers handled each one.
Try asking
- “Create a delivery task for 42 Oak Street, window 2 to 4pm”
- “Which tasks are still unassigned for this afternoon?”
- “Find the recipient with phone 555 0134 and show their tasks”
AI tools
Onfleet tools for your AI agents
78 tools are ready to call through Elaichi's MCP endpoint the moment you connect Onfleet, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Onfleet gets you
6 screens from the product, each doing one job for your Onfleet account.
The agent
Ask about deliveries, get live Onfleet answers.
Type a question in plain language and see the current state of tasks and drivers.
- tasks
- workers
- destinations
- recipients
Ask Elaichi to work across your apps.
Create a delivery task for 42 Oak Street, window 2 to 4pm
Which tasks are still unassigned for this afternoon?
Find the recipient with phone 555 0134 and show their tasks
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Onfleet endpoint for every MCP client.
Claude, ChatGPT and Cursor connect through one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
78 Onfleet tools, no code to write.
Tasks, workers, destinations, recipients and teams, covered from creation through completion.
- Create a Onfleet task
- List all Onfleet tasks
- Get single Onfleet task by ID
- Update a Onfleet task by ID
Toolboxes
Each team gets its own Onfleet toolbox.
Dispatch, support and fleet each see only the Onfleet tools their work needs.
- Dispatch
- Support
- Fleet
- Operations
Shared connections
Teammates dispatch without touching the API key.
One person connects Onfleet, shares it with teams, and nobody else sees a credential.
- Dispatch
- Support
- Fleet North
- Fleet South
Audit log
Every Onfleet change names who made it.
When, who, what happened and which task, kept in an append-only log.
- 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 runs the delivery digest itself.
Onfleet tasks are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Onfleet digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tasks
Onfleet
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
Onfleet
Queued
Collections and dashboards
Onfleet delivery health, computed without a model.
Four metrics, 14 days of tasks created, and a breakdown by team, refreshed on schedule.
Onfleet health
Refreshed 4 minutes ago · every 15 minutes · from the tasks collection
Tasks
1,284 ↓ 12%
Workers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tasks created
Last 14 days
By team
Share of activity
Dispatch 34%
Support 27%
Fleet North 21%
Fleet South 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Onfleet to Claude?
In Elaichi, choose Onfleet and paste an API key from your Onfleet dashboard settings, which is the only sign-in step Onfleet asks for. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Your Onfleet tasks, workers, and recipients are available in Claude from that point.
Does Onfleet work with ChatGPT and Cursor as well as Claude?
Yes. Once Onfleet 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 Onfleet once and every client picks it up.
What can an AI agent actually do with my Onfleet data?
An agent can create delivery and pickup tasks in Onfleet, update their time windows and notes, clone them, auto-assign them to available drivers, and mark them complete. It can look up a recipient by phone number, check the status of a bulk task upload, and add or update drivers and teams. Short, concrete asks such as "show unassigned tasks for this afternoon" work better than long paragraphs.
Does connecting Onfleet give the AI access to my whole fleet?
The AI can only reach what the Onfleet API key you pasted can reach, and each person signs in to Elaichi as themselves before they use it. Elaichi can narrow that access further, for example to reading tasks only, but it can never widen what Onfleet itself allows.
Can I stop an agent from deleting or changing things in Onfleet?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and creating Onfleet tasks while blocking deletion of tasks or workers. A restricted action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to an Onfleet connection when someone leaves?
Offboarding a person in Elaichi ends their access to Onfleet through every client at once. If they had shared an Onfleet connection with a team, it keeps working for everyone else. Disconnecting Onfleet once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the Onfleet MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Onfleet 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.
Put Onfleet 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.