Connect Motive to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Motive, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Motive + Meta Muse

Let your AI read your Motive fleet: where every truck and driver is, Hours of Service clocks and violations, inspection reports, safety events, fault codes, IFTA mileage and fuel purchases. Read-only, with a company API key.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

MOTIVE_API_KEY

Step 1 — Get credentials

Setting up takes about 3 minutes. You need an admin role in Motive (formerly KeepTruckin) to create a company API key in the Motive dashboard.

1. In the Motive dashboard open Admin → Developers → API Access and create a company API key. Give it read access and the scopes for the data the AI should see: vehicles, locations, users, HOS, IFTA, fuel, inspections, safety events, fault codes, assets and groups. A key can also be limited to some groups; the AI then sees only those.
2. Copy the key from the one-time dialog, because the full key is shown only once, and paste it into MOTIVE_API_KEY: the key alone, without spaces or a header name such as X-Api-Key. AnythingMCP sends it as the X-Api-Key header.
3. Install the connector and run motive_list_vehicles to check the connection.

Cloud and self-hosted work the same way: the API key is the only setting.

Keys expire and cannot be edited: a key expires on the schedule chosen when it was created, and Motive warns admins a week before. Its scopes cannot be changed later: to reach more data, create a new key and paste it into MOTIVE_API_KEY.

Ids: vehicles, users and assets have numeric Motive ids. The unit number a dispatcher uses ("Truck 12") is the vehicle number; motive_lookup_vehicle turns it into an id. Drivers are users with the role driver.

Dates, time zones and units: date filters are YYYY-MM-DD, and most reports default to the last 7 days; updated_after takes an ISO 8601 timestamp. Most tools let the AI choose the time zone of the timestamps (sent as X-Time-Zone, for example America/New_York) and metric or imperial units (sent as X-Metric-Units: kilometres and litres, or miles and gallons). Name the time zone and the units in your prompt when they matter. Hours of Service durations in motive_list_available_time are in seconds.

Paging: lists return 25 records per page by default and at most 100 (per_page), and page with page_no. Each answer carries pagination with per_page, page_no and total; the AI asks for the next page while there are more records than it has seen.

Location history: motive_get_vehicle_location_history reads one vehicle over at most 3 months; keep the range short for a readable answer. Motive accepts at most 10 simultaneous requests on this endpoint.

Some data needs hardware or a plan: AI dashcam safety events (cell phone use, seat belt, tailgating and so on), Vehicle Gateway locations (motive_list_vehicle_gateway_locations; vehicles on other ELDs answer through motive_list_vehicle_locations) and the locations of trailers with an asset gateway.

EU accounts are not covered: the connector calls https://api.gomotive.com; accounts on Motive's EU platform use a different host.

Common errors: a 401 means Motive refused the key: it was not copied in full, has expired or was revoked, or was pasted with the X-Api-Key header name. A 403 means the key is valid but lacks the scope for that data: create a new key with that scope. A 404 means there is no record with that id: use the numeric id, not the vehicle number or the driver's name. When Motive rate limits the key, wait a minute, ask for fewer pages and try again.

What it reads: vehicles with VIN, make, model, plate, fuel type, ELD device and driver; the current location of every vehicle and driver, and the route of a vehicle over a period; drivers, fleet users and admins; Hours of Service clocks (who can still drive and for how long), daily logs and violations; IFTA trips and mileage per state or province; fuel purchases; inspection reports (DVIRs) with their defects; safety events with coaching status and media links; engine fault codes; driving periods, including personal conveyance, yard moves and unidentified driving; trailers and other assets with their last location; and the groups the fleet is split into.

Read-only: every tool only reads, and none is switched off at install. Nothing is changed in Motive: creating or editing vehicles, users, groups, geofences, fuel purchases or inspection reports, messaging drivers, dispatches and engine immobilizer commands are left out.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Motive tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "Where is Truck 12 right now, and who is driving it?"
• "Which drivers can still drive today, and for how long?"
• "Which drivers had hard braking or cell phone events last week?"
• "Which vehicles have inspection reports with defects or open fault codes?"
• "How many miles did each truck drive per state last quarter for the IFTA return?"

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude