Set up the Motive MCP

Overview

The Motive MCP exposes your fleet, compliance, safety, dispatch, and workforce data to an AI client through the model context protocol, an open standard for connecting assistants to external systems.

Once connected, your assistant can query Motive directly instead of working from data you copied into the conversation.

You can ask questions such as:

• Which drivers are within two hours of their HOS limit?
• List yesterday's DVIRs with unresolved defects.
• Which trucks entered the Dallas yard this morning?
• Create a geofence around our new Reno yard.
• Message the Southwest team about the weather delay.

Because the Motive MCP uses the MCP standard, the same connection works with any MCP-compatible client.

Before you begin

• The Motive MCP is generally available for fleets in the US, Canada, Mexico, and Europe.
• You must connect with a Motive fleet admin account. Driver and fleet-user accounts cannot connect yet.
• Access is currently fleet-wide after connection, regardless of the connected admin's dashboard permission level. Per-role scoping is not available yet.

The Motive MCP endpoint depends on your fleet's region:

• US, Canada, and Mexico: https://mcp.us.gomotive.com/mcp
• Europe: https://mcp.eu.gomotive.com/mcp

Connection details

The Motive MCP is configured as a remote MCP server using the endpoint for your region.

Connect the Motive MCP

Claude

1. Go to Settings > Connectors > Add custom connector.
2. Enter the Motive MCP endpoint for your region:
   • US, Canada, and Mexico: https://mcp.us.gomotive.com/mcp
   • Europe: https://mcp.eu.gomotive.com/mcp
3. Sign in with a Motive fleet admin account when prompted.
4. Approve access if Claude prompts you to do so.

The first connection usually takes about two minutes.

ChatGPT

1. Open Connectors in ChatGPT.
2. Add a custom connector.
3. Enter the Motive MCP endpoint for your region:
   • US, Canada, and Mexico: https://mcp.us.gomotive.com/mcp
   • Europe: https://mcp.eu.gomotive.com/mcp
4. Sign in with a Motive fleet admin account when prompted.

The sign-in prompt appears the first time you use the connector.

Cursor

Add the Motive MCP server to .cursor/mcp.json for a project or ~/.cursor/mcp.json globally.

For the US, Canada, and Mexico:

{
  "mcpServers": {
    "motive": {
      "url": "https://mcp.us.gomotive.com/mcp"
    }
  }
}

For Europe:

{
  "mcpServers": {
    "motive": {
      "url": "https://mcp.eu.gomotive.com/mcp"
    }
  }
}

Cursor prompts you to sign in with your Motive fleet admin account the first time the server is used.

Gemini CLI

For Gemini, add the Motive MCP server with the following configuration or configure it in ~/.gemini/settings.json.

For the US, Canada, and Mexico:

{
  "mcpServers": {
    "motive": {
      "httpUrl": "https://mcp.us.gomotive.com/mcp"
    }
  }
}

For Europe:

{
  "mcpServers": {
    "motive": {
      "httpUrl": "https://mcp.eu.gomotive.com/mcp"
    }
  }
}

Other MCP clients

The Motive MCP works with any MCP-compatible client that supports a remote MCP server. Add the endpoint for your region to the client's MCP or connector settings:

• US, Canada, and Mexico: https://mcp.us.gomotive.com/mcp
• Europe: https://mcp.eu.gomotive.com/mcp

Follow the client-specific instructions to complete OAuth sign-in and approve tool calls.

Verify your connection

1. Open the AI client where you added the Motive MCP.
2. Ask a read-only question that matches your fleet, such as: “Where is truck 4021 right now?”

If the client returns fleet data, the connection is working. If it returns an authentication error, disconnect and reconnect the Motive MCP, then sign in again.

Disconnect or reconnect

To disconnect the Motive MCP, remove it from your AI client's connector or MCP-server settings.

To reconnect, add the Motive MCP endpoint again and complete the OAuth sign-in flow.

If your OAuth session expires or is revoked, disconnect and reconnect, then sign in again.

If you need access removed but your client does not provide a revoke option, ask the connected Motive fleet administrator to review the account's access.

Understand access and permissions

Authentication

• Sign-in uses OAuth against your Motive login.
• The first connection opens a browser window for authentication.
• Only fleet admins can connect today.
• Driver and fleet-user accounts cannot authenticate.

Data visibility

Access currently follows the connected fleet admin's account, but visibility is fleet-wide regardless of that admin's dashboard role. Do not treat the Motive MCP as per-user scoped until per-role permission scoping is available.

Important: The connected fleet admin can expose fleet-wide data, and write actions run under that connected admin's permissions. Do not use the Motive MCP for workflows that require per-user data scoping until per-role permission scoping is available.