Onfleet MCP server

What the model can do

Onfleet last-mile delivery: tasks in a time window by state (unassigned, assigned, active, completed), each with its delivery window, assigned driver and team, delay, and whether it succeeded or why it failed; one task by id or short id; drivers on and off duty with their teams and current task; teams and hubs. Can create a delivery or pickup task (the recipient is texted unless told not to), change a task's notes, window or assignment, force-complete or delete a task, and add a driver, each only when asked. Drivers and teams are named; recipients' names, phones and addresses, and drivers' phones and locations, are never returned.

Reads

• onfleet_tasksOnfleet tasks created (or, for completed tasks, completed) in a time window, oldest created first: id, short id, state, pickup or drop-off…
• onfleet_taskOne Onfleet task by its id or its short id (the code on the tracking link): state, window, driver, team, ETA, delay, and whether it succeeded.
• onfleet_workersOnfleet drivers (workers) by name and id: on or off duty, current task, number of assigned tasks, teams, vehicle type, capacity…
• onfleet_teamsOnfleet teams: id, name, hub, and how many drivers, dispatchers and tasks each has.
• onfleet_hubsOnfleet hubs (the depots tasks start from): id, name, city and postcode, and the teams based there.

Acts, when you ask

These change something in Onfleet. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• onfleet_create_taskCreate an Onfleet delivery or pickup task.
• onfleet_update_taskChange an Onfleet task: its notes, time window, destination (an existing destination id), or its assignment to a driver or team…
• onfleet_complete_taskForce-complete an active Onfleet task as succeeded or failed, on the driver's behalf.
• onfleet_delete_taskDelete an Onfleet task.
• onfleet_create_workerAdd a driver (worker) to Onfleet in one or more teams.

Connect it

First connect Onfleet on Dashboard → Connections, then add Memtro to your client once. The Onfleet tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Onfleet connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which deliveries failed today, and why?
• › Which drivers are on duty right now?
• › Which tasks are running late this afternoon?
• › How many tasks does the North team have?
• › Reassign task 7f3a2b to Sam on the North team

Questions

Is this an official Onfleet MCP server?

No. It is Memtro's MCP server with Memtro's Onfleet connector behind it: the connector reads Onfleet through its API with the credentials you connect on Dashboard → Connections, and Onfleet publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Onfleet?

Only when you ask, and only what it has been granted: create a delivery or pickup task (texts the recipient unless notify_recipient is false); change a task's notes, time window, destination or assigned driver or team; force-complete an active task as succeeded or failed (final); delete an unassigned task (permanent); add a driver to one or more teams (gives them access to the driver app). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Shipping and delivery

• ShipEngine MCP server
• Royal Mail Click & Drop MCP server
• DHL Location Finder MCP server
• EasyPost MCP server
• FedEx MCP server
• Shippo MCP server