Motive MCP integration
Manage Motive fleet vehicles, vehicle locations, drivers, users, and company webhook events.
Sign in, add Motive in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
list_vehicle_locationsList Motive vehicle locations through the v3 Vehicle Gateway endpoint. Use filters for least-privilege location reads. | List Motive vehicle locations through the v3 Vehicle Gateway endpoint. Use filters for least-privilege location reads. |
list_vehiclesList Motive company vehicles, optionally restricted to vehicles updated after a UTC timestamp. | List Motive company vehicles, optionally restricted to vehicles updated after a UTC timestamp. |
get_vehicleFetch one Motive vehicle by exact vehicle ID. | Fetch one Motive vehicle by exact vehicle ID. |
create_vehicleCreate a Motive vehicle using the documented vehicle body. Include gateway and external ID details when required by your account. | Create a Motive vehicle using the documented vehicle body. Include gateway and external ID details when required by your account. |
update_vehicleUpdate a Motive vehicle by exact vehicle ID using documented vehicle fields. | Update a Motive vehicle by exact vehicle ID using documented vehicle fields. |
list_driver_locationsList Motive drivers with current location and vehicle information. Use bounded pages for PII-heavy operations. | List Motive drivers with current location and vehicle information. Use bounded pages for PII-heavy operations. |
create_userCreate a Motive user such as a driver, fleet user, or admin using the documented user body. | Create a Motive user such as a driver, fleet user, or admin using the documented user body. |
update_userUpdate a Motive user by exact user ID. | Update a Motive user by exact user ID. |
Triggers
| Name | Description |
|---|---|
vehicle_location_updatedPoll Motive vehicle locations after an initial baseline. | Poll Motive vehicle locations after an initial baseline. |
webhook_event_receivedReceive Motive company webhook events. Signature verification is not performed by this trigger. | Receive Motive company webhook events. Signature verification is not performed by this trigger. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('motive', 'list_vehicle_locations', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'motive',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Motive MCP server through Weavz?
Yes. Add the Motive integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 8 Motive actions.
What can an AI agent do with Motive?
Available actions include List Vehicle Locations, List Vehicles, Get Vehicle, Create Vehicle, Update Vehicle, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Motive to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Motive, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Motive through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Motive require?
The catalog lists an API key for Motive. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive Motive actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Motive?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What Motive triggers are available?
The catalog lists 2 triggers, including Vehicle Location Updated, Webhook Event Received. Configure the trigger and your event handler before using incoming events to start work.
Connect Motive in minutes
Get 20,000 free action executions every month. No credit card required.