Connect Fleet Comply to Claude and ChatGPT

What you can ask

• “What's overdue in Fleet Comply?”
• “Which registrations and inspections are due in the next 30 days?”
• “Show the compliance report for our Chicago yard.”
• “Find truck 104 in Fleet Comply.”
• “Which drivers' medical cards expire this quarter?”
• “Here's truck 104's new registration. Send it in for review.”

Tools

• List companies. The Fleet Comply companies the signed-in user belongs to, with their role in each.
• Compliance summary. Counts of overdue and due-soon requirements, missing documents (none on file, rejected or expired), documents awaiting approval and critical alerts, plus the most urgent open work items.
• Due dates. Open requirements due between two dates (inclusive), with vehicle, driver or location, owner and document status. Defaults to the next 30 days; also reports how many are overdue from before the range. Lists up to 200 items (25 on a free trial); itemCount is always the full number.
• Compliance report. Open obligations with due date, document status and owner, plus totals (overdue, due in 7/30/60/90 days, missing documents, documents awaiting approval) and a per-location breakdown. A document awaiting approval is not counted as missing. Also returns byOwner (open and overdue counts per owner) for "who owns what". Lists up to 200 rows (25 on a free trial); totals, byOwner and rowCount are always complete.
• Search vehicles, drivers and locations. Find vehicles (unit number, VIN, plate), drivers and locations by name or identifier.
• Approve or reject a document. Approve or reject the document awaiting approval on a requirement. Approve marks it verified and moves the requirement to its next due date (the document's expiration date unless nextDueDate is given). Reject sends the requirement back to needing a document and requires a note.
• Assign a requirement owner. Make one company member responsible for a requirement (they get its alerts and it shows as theirs).
• Mark a requirement complete. Complete a requirement that needs no document, or whose document is already approved, and roll it to its next due date. Requirements that need a document must have one approved first.
• Send documents. The standard way to send documents, one or several (up to 10 files, one per requirement), in one request. Returns one uploadPageUrl for all of them and an uploadId per file. On that page the user drops all the files at once (each is matched to its requirement by filename; iPhone photos are converted) or one per box. Every document stays separate, with its own checks and its own approval. When ONE PDF holds several documents, send it as one upload with documents instead of cycleId and fields: each document's page range, its values and, if known, its cycleId. When the file is attached, Fleet Comply splits the PDF, matches each document to its vehicle or driver and requirement, and puts each one in AI Document Intake for review.
• Attach an uploaded document. Attaches a sent file to its requirement as awaiting approval. With fields (values the user confirmed), Fleet Comply checks them right away. Without them, Fleet Comply reads the document itself, for up to about 25 seconds; past that, the result says it is still reading. Returns the values, a one-line summary and any flags (wrong unit or name, already expired, expires before the due date). For a PDF sent with documents, it splits the file and returns one entry per document (pages, type, what it matched) and a summary such as "5 documents sent: 4 matched, 1 needs a vehicle or driver picked"; each waits for review in AI Document Intake. Never approves.
• Check an upload. The state of an upload: whether it's attached, the values read from it, a summary and any flags, and once attached, documentStatus: awaiting_approval, approved or rejected.
• Get a requirement's document. The current document on file for a requirement (filename, status, document type and number, dates) with a download link that works for 5 minutes. Returns document: null when nothing is on file.
• List alerts. Unresolved operational alerts (open or acknowledged) with alertId, severity, title, message, the vehicle, driver or location and requirement they're about, and cycleId. Most severe and oldest first.
• Change a due date. Correct an open requirement's due date (for example, when the real expiration differs from what's on file). Reminders follow the new date. Not for renewals: a renewal is an approved new document or a completed requirement, which rolls it to the next cycle.
• Add a note. Add a note to a requirement's activity history, for example "shop appointment booked for the 14th". Shown on the vehicle, driver or location page in Fleet Comply.
• Acknowledge or resolve an alert. Acknowledge an open alert (someone is on it; it stays listed) or resolve it (handled; it leaves the list).

Set it up

Connector URL: https://app.getfleetcomply.com/api/mcp

Claude: Settings → Connectors → Add custom connector. Name it Fleet Comply, paste the URL, then connect and sign in with your Fleet Comply account.

ChatGPT: add a connector with the URL above (OAuth sign-in), then sign in with your Fleet Comply account and turn the connector on in a chat.

Microsoft Copilot Studio: add an MCP server tool with the URL above and choose dynamic discovery for sign-in.

Menu names in each assistant can change; look for “connectors” or “apps” in its settings.

Access and security

• Included with paid Fleet Comply plans and active free trials. On a trial, each document page sent through the connector uses one of the trial's AI scan pages.
• You sign in with your own Fleet Comply account. The assistant sees only what you can see in the app: your company, your role and your locations.
• Changes need your go-ahead. The assistant asks before it changes anything, and only roles that can make the change in the app can make it through the connector. It never deletes records, and documents are never approved automatically.
• Each request is authenticated with a short-lived sign-in token. You can disconnect at any time from the assistant's settings.
• How we handle data is described in our Privacy Policy and Terms of Service.

Help

Questions or problems: support@getfleetcomply.com.