Fleetio logoMCP server · Work management

Fleetio MCP server

Fleetio in any MCP client, through Memtro: Fleetio does not publish this server. Memtro's Fleetio connector reads Fleetio through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Fleetio fleet maintenance: vehicles with status, meters and assigned driver, issues, work orders, service history, fuel entries and contacts by name and role. Can comment on a record, report, update, close, resolve and reopen issues, open and update work orders, log service, fuel and meter readings, update, assign and archive vehicles, and approve purchase orders.

Reads

  • fleetio_list_vehiclesFleetio vehicles: name, year, make, model, VIN, plate, status, type, group, latest meter reading, open issue and work order counts…
  • fleetio_list_issuesFleetio issues, newest reported first: number, summary, description, state (Open, Resolved, Closed), priority, vehicle, who reported it…
  • fleetio_list_work_ordersFleetio work orders, most recently changed first: number, status, description, vehicle, vendor, contact's name, issued, scheduled…
  • fleetio_list_service_entriesFleetio service history, most recently completed first: vehicle, vendor, status, completed and started dates, reference, notes and the total cost.
  • fleetio_list_fuel_entriesFleetio fuel entries, newest first: date, vehicle, volume, cost, economy and vendor, with totals.
  • fleetio_list_contactsFleetio contacts (drivers, technicians, staff) by name, with group, job title and role only.
  • fleetio_list_work_order_statusesFleetio work order statuses (id, name, whether it counts as completed…
  • fleetio_list_issue_prioritiesFleetio issue priorities (id, name, whether default): the issue_priority_id for fleetio_create_issue and fleetio_update_issue.
  • fleetio_list_vehicle_statusesFleetio vehicle statuses (id, name, whether default): the vehicle_status_id for fleetio_update_vehicle.
  • fleetio_list_vendorsFleetio vendors (garages, fuel stations, parts suppliers) by name: id, name and what kind of vendor it is (fuel, service, parts, vehicle)…

Acts, when you ask

These change something in Fleetio. 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.

  • fleetio_add_commentAdds a comment to a Fleetio vehicle, issue, work order, service entry or fuel entry, as the key's user.
  • fleetio_create_issueReports a new issue on a Fleetio vehicle or piece of equipment, as the key's user, with a summary and optionally a description, priority and due date.
  • fleetio_close_issueCloses a Fleetio issue (marks it Closed without a repair) with a note, as the key's user.
  • fleetio_resolve_issueMarks a Fleetio issue Resolved (the fault was fixed) with a note, as the key's user.
  • fleetio_reopen_issueReopens a closed or resolved Fleetio issue, as the key's user.
  • fleetio_update_issueChanges a Fleetio issue's summary, description, priority, due date or due meter, assignees, labels or reporter, as the key's user.
  • fleetio_create_work_orderOpens a Fleetio work order on a vehicle with a status (from fleetio_list_work_order_statuses), as the key's user, optionally with a vendor…
  • fleetio_update_work_orderChanges a Fleetio work order's status (for example to Completed), vendor, contact, description, dates, invoice or purchase order number…
  • fleetio_create_service_entryLogs a completed service on a Fleetio vehicle, as the key's user, with the meter reading at the service and optionally the vendor, reference, notes…
  • fleetio_create_fuel_entryLogs a fuel purchase on a Fleetio vehicle, as the key's user, with the date and the odometer reading, and optionally the volume…
  • fleetio_create_meter_entryRecords an odometer or hour-meter reading on a Fleetio vehicle, as the key's user.
  • fleetio_update_vehicleChanges a Fleetio vehicle's name, status, group, type, plate, VIN, make, model, year, colour, ownership or labels, as the key's user.
  • fleetio_assign_vehicleAssigns a Fleetio vehicle to a contact (a driver or operator) from a start time, optionally to an end time, as the key's user.
  • fleetio_unassign_vehicleEnds a Fleetio vehicle assignment now (the assignment id, not the vehicle id), as the key's user.
  • fleetio_archive_vehicleArchives a Fleetio vehicle, as the key's user: it leaves the active fleet and its lists.
  • fleetio_approve_purchase_orderApproves a Fleetio purchase order awaiting approval, by its number, as the key's user (which needs the purchase order approve permission).

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

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

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

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

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

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

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

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 Fleetio 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 vans have overdue issues?
  • › What did we spend on servicing last month?
  • › How much did we spend on fuel in the last 30 days?
  • › Report a brake warning light on van 7, high priority.
  • › Assign van 12 to Priya Sharma from Monday.

Questions

Is this an official Fleetio MCP server?
No. It is Memtro's MCP server with Memtro's Fleetio connector behind it: the connector reads Fleetio through its API with the credentials you connect on Dashboard → Connections, and Fleetio 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 Fleetio?
Only when you ask, and only what it has been granted: comment on a vehicle, issue, work order, service entry or fuel entry; report a new issue on a vehicle or piece of equipment; close, resolve or reopen an issue; change an issue's summary, priority, due date, assignees or labels; open a work order on a vehicle; change a work order's status, vendor, dates or description; log a completed service on a vehicle; log a fuel purchase on a vehicle; record an odometer or hour reading; change a vehicle's name, status, group, plate or labels; assign a vehicle to a driver or end an assignment; archive a vehicle; approve a purchase order. 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 · Work management

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time