# How can a fleet team use Fleetio in ChatGPT?

> Fleetio in ChatGPT answers which vans are overdue for service. Keep the reads open and restrict meter, issue and vehicle writes.

**TL;DR** Fleetio in ChatGPT runs through Elaichi's fleetio connector, which calls the Fleetio API with one API key that carries one Fleetio user's role. Create that key from a dedicated user, then give the fleet role an allow rule that names the reminder, issue, work order, inspection, fuel and expense reads. Block rules keep meter entries, issue closes and vehicle archives out of reach, and Fleetio's own read-only MCP server covers teams that only ask Fleetio questions.

## Why a fleet manager wants Fleetio in ChatGPT

Emily Carter manages the service vans for a plumbing and HVAC company that runs crews out of four yards. Her Monday questions repeat. Which vans are overdue for an oil change? Which issues are still open from last week? What failed on Friday's inspections? What did fuel cost per van last month? Each answer lives in Fleetio, on a different screen. Fleetio in ChatGPT puts those lookups in the chat where she already plans the week.

MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. Fleetio publishes one: its help center documents the Fleetio MCP Server, which connects AI assistants such as Claude and ChatGPT to a Fleetio account and is read-only ([help.fleetio.com](https://help.fleetio.com/en_US/integrations/fleetio-mcp-server), checked November 2026). For a team whose questions stay inside Fleetio, that server may be enough.

[Elaichi's `fleetio` connector](/connectors/fleetio/) is the other path. It signs in with a Fleetio API key and carries reads, writes and deletes across vehicles, service reminders, issues, work orders, inspections, meter, fuel and expense entries. Emily's team needs the reads. A few writes need a decision before rollout.

## Whose Fleetio user should hold the API key?

Create the key from a dedicated Fleetio user with a narrow role, never from Emily's own login. Fleetio's Permissions page says an API key is associated with a single Fleetio user. That user's role applies in the web app, Fleetio Go and the API alike, and a call outside it returns 403 Forbidden ([developer.fleetio.com](https://developer.fleetio.com/docs/overview/permissions), checked November 2026).

Fleetio's own security guide gives the steps. Add a Contact with access to Fleetio enabled, give it a role with the minimum permissions it needs, then sign in as that user and create the key. The guide also warns that someone holding a key can impersonate its user and reach that user's data ([developer.fleetio.com](https://developer.fleetio.com/docs/overview/security), checked November 2026). A key from an account owner carries the owner's reach.

To create the key, the dedicated user opens their account settings, then Manage API Keys, then + Add API Key, and sets a label and an API version. Every request also needs an Account-Token header, and the token sits at the bottom of the same page ([developer.fleetio.com](https://developer.fleetio.com/docs/overview/quick-start), checked November 2026).

That Fleetio role is the ceiling for the whole team. If it allows no meter entries, no Elaichi rule or access request can log one.

## Which Fleetio reads answer the Monday fleet check?

Nine list tools answer most of Emily's questions. `list_all_fleetio_service_reminders` returns each reminder's next due date, next due meter and status: ok, due soon, overdue or snoozed. Filter it on overdue and the oil change question is one call.

`list_all_fleetio_issues` and `list_all_fleetio_work_orders` return issues and work orders a page at a time, up to 100 per page. ChatGPT pages through them to answer "what is still open on van 214". `list_all_fleetio_submitted_inspection_forms` returns each inspection's failed items, the vehicle, the person who submitted it and any linked work order.

Cost questions go to three more reads. `list_all_fleetio_fuel_entries` filters by vehicle, vendor and date, and returns volume and total amount. `list_all_fleetio_expense_entries` filters by vendor, vehicle, entry type and date. `list_all_fleetio_service_entries` returns each service's total, vehicle and vendor. `list_all_fleetio_vehicles` and `list_all_fleetio_meter_entries` fill in names and odometer history.

## Which Fleetio writes deserve a second look?

Meter entries, issue status changes and vehicle archives are the writes that change maintenance quietly. The catalog tiers `fleetio_vehicles_archive` destructive alongside the delete tools.

| Kind | Example tools | For the fleet role |
|---|---|---|
| Maintenance reads | `list_all_fleetio_service_reminders`, `list_all_fleetio_issues`, `list_all_fleetio_work_orders`, `list_all_fleetio_submitted_inspection_forms` | Allow |
| Cost and meter reads | `list_all_fleetio_fuel_entries`, `list_all_fleetio_expense_entries`, `list_all_fleetio_service_entries`, `list_all_fleetio_meter_entries`, `list_all_fleetio_vehicles` | Allow |
| Meter writes | `create_a_fleetio_meter_entry`, `update_a_fleetio_meter_entry_by_id`, `delete_a_fleetio_meter_entry_by_id` | Restrict |
| Issue status | `fleetio_issues_close`, `fleetio_issues_resolve`, `fleetio_issues_reopen` | Restrict |
| Reminder changes | `update_a_fleetio_service_reminder_by_id`, `delete_a_fleetio_service_reminder_by_id` | Restrict |
| Vehicles | `fleetio_vehicles_archive`, `fleetio_vehicles_restore`, `delete_a_fleetio_vehicle_by_id` | Restrict |

Meter entries drive the schedule. Fleetio does not let odometer readings go backwards, and an update that puts one out of order returns HTTP 422 ([developer.fleetio.com](https://developer.fleetio.com/docs/guides/meter-entries/resolving-invalid-meter-entries), checked November 2026). When meter history changes, a reminder's due meter updates with it ([help.fleetio.com](https://help.fleetio.com/en_US/service-reminder-reset-troubleshooting), checked November 2026). Forecasting projects due dates from the latest reading ([help.fleetio.com](https://help.fleetio.com/en_US/service-reminder-forecasting), checked November 2026). A reading with one extra digit shifts every meter-based reminder on that van.

Issue status is a judgment call. Fleetio's Issue Status article says Resolved means fixed through a service entry or work order. Closed means acknowledged and not going to be repaired, like a door dent ([help.fleetio.com](https://help.fleetio.com/en_US/issue-status), checked November 2026). A model that closes the wrong issue clears it from the Open list with no repair done.

Vehicles carry two traps. Archiving disables a vehicle's service and renewal reminders and their emails. Deleting works only after archiving and cannot be undone. Restoring adds the vehicle back to the plan and raises the monthly bill on a prorated basis ([help.fleetio.com](https://help.fleetio.com/en_US/archive-restore-or-delete-vehicles), checked November 2026).

## Writing the Fleetio rules on the fleet role

One allow rule on the fleet role gives Emily's team the Fleetio reads and nothing else. A restriction is a rule naming which connectors and which individual tools a target may reach. In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything. So the fleet team needs its own role, and each member holds exactly one.

Name the nine read tools in the rule. The same rule, or a second allow rule on the role, must also name every other app the fleet team uses, as whole connectors. In Elaichi, once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role. A calendar or parts supplier connector left off the list is lost to the role. Do not name the fleetio connector whole and some of its tools in one rule. Elaichi refuses that overlap on a new rule.

Then add block rules on the meter, issue status, reminder and vehicle tools from the table. Within a layer, a block always beats an allow. If someone later widens the allow rule to all of Fleetio, those tools stay restricted. [Restricting single tools versus whole apps](/blog/per-tool-vs-per-app-restrictions/) compares the two shapes. A restriction change takes effect within about two minutes.

## Sharing the Fleetio connection with the fleet desk

A fleet admin connects the fleetio connector once with the dedicated user's credentials, then shares it with the team at `use`. A shared connection runs on its owner's credential, so every member's call reaches Fleetio as the same Fleetio user. In Elaichi, a call from an MCP client is recorded under the person who signed in, with surface `mcp` and the OAuth client named. Fleetio sees one user; Elaichi keeps the names.

Pick an owner who will stay. Offboarding can transfer a shared connection to another active member, and the shares stay as they were.

Every organization uses one address: `https://api.elaichi.ai/mcp`. On ChatGPT Business, only admins and owners create and publish custom apps for the workspace, and members then connect the published app ([help.openai.com](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt), checked October 2026). Each member signs in with their own OAuth grant, the sign-in that ties their Elaichi identity to ChatGPT. [Connecting Elaichi to ChatGPT](/blog/connect-elaichi-to-chatgpt/) has the steps.

In Elaichi, connected tools are never listed one by one, however few there are. On Elaichi's consent screen, "Use your connected apps" runs writes and deletes as well as reads. So the consent screen cannot hold ChatGPT to Fleetio reads; the fleet role's rules do that.

## Testing the fleet role before the Monday check

Sign in from a test account on the fleet role and ask ChatGPT which vans have overdue service reminders. The read should run. Then search for "meter" and "archive". A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema.

Then read the audit trail. Elaichi writes one entry for each connected-tool call that reaches execution (a call refused earlier writes none). Each entry records the tool, the connection reached, the outcome and the client, plus the one path argument that names the object, as the target id, and nothing else about the arguments. [What an AI audit log must capture](/blog/what-an-ai-audit-log-must-capture/) lists what to check in those rows.

Mind both rate limits. Fleetio sets API limits by plan and answers 429 with a Retry-After header ([developer.fleetio.com](https://developer.fleetio.com/docs/overview/rate-limiting), checked November 2026). Its help center puts the plan limit at 50 requests a minute on Professional and 250 on Premium ([help.fleetio.com](https://help.fleetio.com/en_US/integrations/fleetio-mcp-server), checked November 2026). Elaichi allows 120 MCP requests every 60 seconds per OAuth grant. Every member's call runs on the same key, so the whole team shares one Fleetio limit.

When a dispatcher later needs to log meter readings, they file an access request. An admin approves it in the console, under Governance, then Access requests. The grant lifts that one tool for that one person, and the role is not edited. It works only if the dedicated Fleetio user's role allows meter entries too.

## When Fleetio's own MCP server is enough

If the team only asks Fleetio questions, Fleetio's MCP Server may be all it needs. Its sample prompts are Emily's list: overdue PM reminders, open work orders and who holds them, failed inspections and fuel spend per vehicle. It is on Professional and Premium plans. Each person signs in with their own Fleetio login, needs no API key and sees what their own Fleetio role allows ([help.fleetio.com](https://help.fleetio.com/en_US/integrations/fleetio-mcp-server), checked November 2026). That is one vendor, per-person Fleetio permissions and nothing to restrict.

Fleetio's help article also says that server cannot create, edit or delete anything. A team that wants one narrow write, such as a dispatcher logging meter readings, needs a connector that calls the Fleetio API.

Elaichi earns its place when the question crosses apps or clients. The van is in Fleetio, the job is in the scheduling app and the invoice is in accounting. One endpoint serves ChatGPT, Claude, Cursor and Microsoft Copilot with one set of rules and one audit trail. [Running vendor MCP servers through Elaichi](/blog/vendor-mcp-servers-through-elaichi/) explains how Elaichi brings a remote MCP server under the same rules. If one person only wants to try a few lookups, [you may not need a control plane at all](/blog/when-you-dont-need-an-mcp-gateway/). The rest of the stack is in the [900+ connectors](/connectors/).

## FAQ

### Does Fleetio have its own MCP server?

Yes. Fleetio's help center documents the Fleetio MCP Server at https://mcp-server.fleetio.com/mcp, for Professional and Premium plans (checked November 2026). It connects Claude, ChatGPT and other AI assistants to a Fleetio account and is read-only. Each person signs in with their own Fleetio login and sees what their Fleetio role allows.

### Whose permissions does a Fleetio API key carry?

A Fleetio API key belongs to one Fleetio user and carries that user's role and permissions, the same in the web app, Fleetio Go and the API. A call outside them returns 403 Forbidden. Fleetio recommends a dedicated user with minimum permissions for each app that calls its API (checked November 2026).

### What happens if an AI enters a wrong odometer reading in Fleetio?

Fleetio requires odometer readings to increase by date, and an update that puts a reading out of order returns HTTP 422. Marking the bad reading void makes Fleetio skip it. Service reminder due meters follow meter history, and forecasting uses the latest reading, so one typo shifts maintenance dates (checked November 2026).

### What is the difference between closing and resolving a Fleetio issue?

In Fleetio, Resolved means the issue was fixed through a service entry or a work order. Closed means someone acknowledged it and it will not be repaired that way, such as a door dent nobody plans to fix (checked November 2026). A closed issue leaves the Open list with no repair behind it.

### How quickly does a new Fleetio restriction take effect in Elaichi?

A restriction change in Elaichi takes effect within about two minutes, so test a new rule after that window. Revoking a share is faster: in Elaichi, revoking a share or disconnecting an account takes effect on the caller's next call.

## Read next

- [Read-only ChatGPT access to your company apps](/blog/make-chatgpt-read-only-in-company-tools/) — Read-only ChatGPT access comes from a restriction rule on a role, not from a consent checkbox or a client setting that sounds like one.
- [Share an MCP connection without the API key](/blog/share-an-mcp-connection-without-the-api-key/) — How to share an MCP connection without the API key in Elaichi: grant a teammate use of a connected account, and take that access back.
- [Vendor MCP servers: why run them through Elaichi](/blog/vendor-mcp-servers-through-elaichi/) — Vendor MCP servers bring the vendor's own tools. Through Elaichi they also get one address, per-person sign-in, tool rules and one audit log.
