Claude FlitIQ connectorWhat Claude can do in your FlitIQ account.
The Claude FlitIQ connector exposes 7 tools. 6 read public FMCSA records on a U.S. motor carrier, from safety scores to insurance and authority, and 1 writes, adding a carrier to your saved list. Here is what Claude checks, what it saves, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude FlitIQ connector changes for carrier vetting
Brokers, shippers and 3PLs use FlitIQ to check a trucking company before booking a load. With this connector, you give Claude a DOT number, an MC number or a company name and ask your question in plain words. Claude pulls the same carrier data the FlitIQ web and iOS apps show, puts it side by side, and can file the carrier on your list.
Clear a new carrier before the load goes out. A freight broker types a DOT number; Claude reads the safety picture with flitiq_get_safety and the active policies with flitiq_get_insurance, and sets both side by side.
Find the right company first. Only a company name to go on? flitiq_search_carrier returns up to 20 matches, and Claude continues with the one you pick, for example into flitiq_get_inspections.
Keep a shortlist. Once a carrier passes, flitiq_save_carrier adds it to your saved carriers with a note, such as a reminder to call back next quarter.
What it will not do: the publisher rules out bulk exports, CSV downloads and any "list every carrier" operation; every lookup is one carrier at a time. Nothing runs on its own either, Claude acts only while it answers. For recurring checks across many records, an automation platform is the better fit; the Integrations hub lists the ones we cover.
Five words before you connect
The Claude vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
- Tool
- One named capability the connector opens to Claude. Claude chooses the ones it needs by itself; the directory lists them by name.
- Authorization
- The step where you hand Claude access to your FlitIQ account. It is granted once per person, and it can be withdrawn the same way.
- Approval
- The confirmation Claude waits for before changing anything in your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as FlitIQ.
Connect FlitIQ to Claude in three steps
- 01
Find FlitIQ in Claude Desktop
This one is a desktop extension, so open the Claude Desktop app, go through Customize then Connectors, and look for FlitIQ in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on first.
- 02
Start the connection
Click Connect on its row and give FlitIQ the access it asks for. If the link breaks later, use Disconnect and connect again; access can also be withdrawn from your FlitIQ account settings.
- 03
Check what you hand over
Read what FlitIQ requests before you accept: the service, not Claude, decides what the access covers. That screen can announce wider permissions than Claude uses day to day; approval per action stays the default rule.
The 7 tools, grouped by what they do
FlitIQ gives Claude 7 tools: 6 that read your account, 1 that change something in it.
Two groups: six tools that look up a carrier and one that writes to your saved list. Names stay exactly as Claude shows them.
- 6 read
- 1 write
What Claude reads (6)
6 toolsSix tools that consult FMCSA-based records on one carrier at a time, without changing anything.
flitiq_search_carrier
Finds motor carriers from a company name, a DOT number or an MC number and returns up to 20 matches, so Claude can settle on the exact company before digging further.
flitiq_get_safety
Brings back a carrier's CSA BASIC scores, out-of-service rates, its safety rating and crash totals, all in one call for a single carrier.
flitiq_get_insurance
Lists the active liability (BIPD), cargo and trust policies on file, with the insurer's name, the policy number, the coverage amount and any cancellation date.
flitiq_get_inspections
Pulls up to the 50 latest roadside inspections, each with its out-of-service count and number of violations, for one carrier at a time.
flitiq_get_crashes
Retrieves up to 50 of the most recent reported crashes for a carrier, with the number of fatalities and injuries for each. The crash totals themselves come with the safety tool.
flitiq_get_authority
Shows whether common, contract and broker operating authority is in place, docket by docket. Like the other lookups, the publisher annotates it as read-only: it consults public FMCSA-based records and leaves your account as it was.
What Claude writes (1)
1 toolOne tool that adds a row to your saved carriers. No source describes a confirmation for it: the general rule below applies.
flitiq_save_carrier
Approval: see the ruleWrites the carrier into your FlitIQ saved list, with an optional note attached. If it is already there, the publisher says the tool reports it as already saved rather than adding it twice.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account in your place. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, for instance keep lookups open and shut writing, and nobody overrides that from a personal account. Claude also works with your access only: the tools answer for the FlitIQ account tied to your API key, nothing wider.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is published nowhere: it is a real hole in the catalogue.
What is published is the general rule: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile, while desktop extensions such as this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector before members connect. For this one's current state, check its sheet in the official directory. Only its publisher documents it; no Claude help page covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a carrier's insurance lapses or a new inspection is filed.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit, and Anthropic notes on every sheet that it neither picks a publisher's tools nor guarantees how they behave. Connect only what comes from a publisher you trust, here SmartLink Basics, LLC. To compare with a connector from another publisher, see the Claude affinity connector page.
Need help connecting FlitIQ to Claude?
A person reads every message.