DIMO MCP server
DIMO is an open protocol using blockchain to establish universal digital vehicle identity, permissions, data transmission, vehicle control, and payments. Developers use DIMO to build apps based on connected vehicles around the world while the vehicle owners benefit from monetizing their vehicle data.
DIMO is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.
- Tools
- 38
- Works with
- Any MCP client
- Auth
- Custom auth
- License
- MIT, open source
- Updated
- September 2026
About the DIMO MCP server
Connect DIMO once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches DIMO and 760+ other apps over a single connection, on our cloud or a self-hosted install.
Tools
DIMO tools your AI can run
Once connected, your assistant can call any of these DIMO actions by asking in plain language.
Attestation : Create VIN VC
Generates the VIN VC for a given vehicle.
1 field
Device Definitions : Decode VIN
Submits a decoding request for vehicle identification number, returns the device definition ID corresponding to the VIN.
2 fields
Device Definitions : Lookup
Search for device definitions by query and filters.
6 fields
Token Exchange : Get Vehicle JWT
Creates a token exchange to obtain a Vehicle JWT.
1 field
Identity : Custom Query
Custom Identity Query.
2 fields
Identity : Total Vehicle Count
Get total vehicle count.
Identity : Get Developer License Info
Get developer license info by tokenId.
1 field
Identity : Get Vehicle By Dev License
Get vehicles by developer license 0x address.
1 field
Identity : Get Total Vehicle Count For Owner.
Get total vehicle count for an owner.
1 field
Identity : Get Vehicle MMY By Owner
Get vehicle MMY by owner address.
1 field
Identity : Get Vehicle MMY By TokenId
Get vehicle MMY by tokenId.
1 field
Identity : Get SACD For Vehicle
Get SACD for a vehicle by tokenId.
1 field
Identity : Get Rewards By Owner
Get rewards by owner address.
1 field
Identity : Get Reward History By Owner
Get reward history by owner address.
1 field
Identity : Get Device Definition
Get device definition by vehicle tokenId.
1 field
Identity : Get Device Definition By DefinitionId
Get device definition by definitionId.
1 field
Identity : Get Owner Vehicles
Get vehicles owned by an address.
1 field
Identity : Get Developer Shared Vehicles From Owner
Get vehicles shared with a developer license from an owner.
2 fields
Identity : Get DCNs By Owner
Get DCNs by owner address.
1 field
Telemetry : Custom Query
Query DIMO Telemetry API using a custom GraphQL query.
3 fields
Telemetry : Available Signals
Get a list of available signals for a specific vehicle.
1 field
Telemetry : Signals
Get a selection of available signals for a specific vehicle.
4 fields
Telemetry : Daily Avg Speed
Get the average speed of a vehicle over a specific time period.
3 fields
Telemetry: Events
Get the vehicle events over a specific time period.
3 fields
Telemetry : Max Speed
Get the maximum speed of a vehicle over a specific time period.
4 fields
Telemetry : VIN VC Latest
Get the latest VIN and Vehicle Configuration for a specific vehicle.
1 field
Vehicle Events: List Webhooks
List all webhooks.
Vehicle Events: Create/Update Webhook (Numeric)
Create a new webhook or update existing one for numeric vehicle signals. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
10 fields
Vehicle Events: Create/Update Webhook (Boolean)
Create a new webhook or update existing one for boolean vehicle signals. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
10 fields
Vehicle Events: Create/Update Webhook (Events)
Create a new webhook or update existing one for vehicle events like harsh braking, acceleration, etc. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
8 fields
Vehicle Events: Delete Webhook
Delete a webhook.
1 field
Vehicle Events: List Signals
List all signals.
Vehicle Events: List Subscribed Vehicles
List vehicles subscribed to a webhook.
1 field
Vehicle Events: List Vehicle Subscriptions
List all subscriptions for a vehicle.
1 field
Vehicle Events: Subscribe Vehicle
Subscribe a vehicle to a webhook.
2 fields
Vehicle Events: Subscribe All Vehicles
Subscribe all vehicles to a webhook.
1 field
Vehicle Events: Unsubscribe Vehicle
Unsubscribe a vehicle from a webhook.
2 fields
Vehicle Events: Unsubscribe All Vehicles
Unsubscribe all vehicles from a webhook.
1 field
Triggers
DIMO events your agent can watch
These start a run the moment something happens in DIMO, so work gets picked up on its own.
Battery is Charging Trigger
Triggers when vehicle battery charging status changes (True/False).
4 fields
Battery Current Power Trigger
Triggers when vehicle battery current power meets the specified condition.
5 fields
Charge Level Trigger
Triggers when vehicle battery charge level meets the specified condition.
5 fields
Fuel System Absolute Level Trigger
Triggers when vehicle fuel system absolute level meets the specified condition.
5 fields
Fuel System Relative Level Trigger
Triggers when vehicle fuel system relative level meets the specified condition.
5 fields
Ignition Status Trigger
Triggers when vehicle ignition status changes (ON/OFF).
4 fields
Odometer Trigger
Triggers when vehicle odometer meets the specified condition.
5 fields
Speed Trigger
Triggers when vehicle speed meets specified conditions.
5 fields
Tire Pressure Trigger
Triggers when vehicle tire pressure meets the specified condition.
6 fields
Give your assistant DIMO
Connect DIMO once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.
DIMO MCP, answered.
No. That is the point of it. One Activepieces server exposes DIMO alongside every other piece you connect, so your client keeps a single connection.