# Motive MCP server

Source: https://agentic-cmms.klementine.xyz/integrations/motive

> Connect Motive to Claude, ChatGPT and other AI agents. Ask about DVIRs, fault codes, engine hours and safety events, and plan repairs sooner.

Motive, once known as KeepTruckin, is a fleet operations platform for trucking, construction, oil and gas, and field service companies. Its vehicle gateways and ELDs record hours of service, location, engine data and fault codes. Drivers complete DVIRs in the Motive Driver app, and AI dashcams flag unsafe driving. Fleet managers, safety teams and workshop leads all use it, each for different reasons. Getting a joined-up answer means switching between their views and stitching the results together.

Agentic CMMS gives Claude, ChatGPT and other AI agents access to Motive. Your team asks about trucks, drivers and defects in plain words, and the agent gathers the facts from across the account.

## What your AI agent can do with Motive

- **Close out DVIR defects.** "Which DVIR defects from the last week are still open, and which trucks have more than one?"
- **Read fault codes.** "List active fault codes on the tractor fleet, most frequent first."
- **Track engine hours.** "Which yard trucks logged the most engine hours this month?"
- **Check available hours.** "Which drivers in the Midlands group can still drive four hours today?"
- **Review safety events.** "Summarise harsh braking and speeding events per driver this month, worst first."
- **Find a truck.** "Where is unit 508, and when did it last leave the yard?"
- **Spot idle assets.** "Which trailers have not moved in 14 days?" Useful before you hire extra trailers for a busy week.
- **Check a vehicle before dispatch.** "Does truck 412 have any open defects or active fault codes?" The agent gives a yes or no, then the detail behind it.

## Motive with your other systems

- Raise a repair in [Fleetio](/integrations/fleetio) for every open DVIR defect, with the driver's comment and the odometer reading.
- See trucks tracked in Motive alongside equipment in [Samsara](/integrations/samsara) or vans in [Geotab](/integrations/geotab) when different divisions use different providers.
- Post the morning list of trucks with open defects to the workshop channel in [Slack](/integrations/slack) before the first load goes out.
- Compare engine hours from Motive with the service history in [Fleetio](/integrations/fleetio), and list the trucks that have run longest without a visit to the shop.

## For the workshop and the safety office

Motive data serves two teams with different needs. The workshop wants defects, fault codes and engine hours so it can plan repairs before a roadside breakdown. The safety office wants driving events and hours of service so it can coach drivers and stay compliant. One platform, two audiences.

Tool permissions let you give each team only what it needs: the workshop sees vehicles, the safety office sees drivers, and you choose who sees both. Each person approves their own agent, and every request lands in the activity log.

## Questions and answers

### Can Claude read DVIRs from Motive?

Yes. The agent lists driver vehicle inspection reports with their defects, and shows which defects are still open and which vehicles they belong to.

### Can an AI agent check hours of service in Motive?

Yes, for the roles you allow. The agent reads drivers' available hours, so a dispatcher can check who can still take a load before assigning it.

### Does the agent see Motive safety events?

It sees the safety events Motive records, such as harsh braking or speeding, with their time and vehicle. Owners and admins decide which roles may use this tool and can block individual people.