Connecting Motive MCP to Claude

Motive MCP connects your live Motive fleet data directly to Claude. Once connected, you can ask questions about your drivers, vehicles, HOS compliance, safety events, dispatch, and more in plain English and get answers grounded in your live Motive data without opening the Motive dashboard.

Setup requires two roles. A Claude admin must add Motive as a connector in Claude first. Then each user signs in with their own Motive credentials to activate the connection.

Note: Only fleet admin accounts on the Motive side can authorize the connection at this time. Fleet managers and operators are not yet supported.

For Claude Admin: Add Motive as a Connector

A Claude admin completes this step once for the workspace.

1. Click + in the Claude toolbar, then select Connectors.

2. Click + in the Connectors panel, then select Add custom connector.

3. In the Add custom connector dialog, fill in the following:

• Name: Motive (or any name you prefer)
• MCP Server URL: https://mcp.us.gomotive.com/mcp
• OAuth Client ID and OAuth Client Secret: Leave both fields blank.

4. Click Add. You are redirected to the Motive login screen. Sign in with your Motive credentials.

5. On the consent screen, review the data scopes being requested, then click Authorize.

Motive is now added as a connector in Claude. Users in the workspace can see it in their connectors list.

For Users: Enable the Motive Connector

Once the Claude admin has completed Step 1, each user enables the connector in their own Claude session.

1. Click + in the Claude toolbar and select Connectors. Motive Public MCP appears in your connectors list.

2. Toggle Motive Public MCP on.

Test Your Connection

To confirm the connection is working, ask Claude: "Give me a morning brief on my fleet performance from yesterday."

Claude will respond with a live summary of your fleet data.

Notes Session persistence: Your session renews silently in the background every two hours. You will not need to re-authenticate unless you explicitly revoke access. Revoking access: To disconnect Motive from Claude, remove the connector from within Claude. This immediately ends the active session; the next attempt to use Motive data will prompt re-authentication. Data visibility: At this time, connected users see fleet-wide data regardless of their role-based permissions inside Motive. Role- and region-based scoping is planned for a future update.

 

Share this with others