Fleet-MCP
Enables AI assistants to interact with Fleet Device Management for device management, security monitoring, and compliance enforcement.Read full description
SimplyMinimalLABSCO SUMMARY
Revocation by removing the connector is simple and worth knowing, because there is no separate dashboard for it.
Some vendors give you a token list to prune; Motive's answer is that deleting the connector in the client is the revocation, effective at once. That is fine as long as you know it — there is no second place to check.
What it is
Motive's hosted endpoint for their fleet management platform. It appears in Claude as 'Motive Public MCP'. Motive publishes no per-tool list.
What you get
Access to the Motive platform through the connector.
Requirements
OAuth 2.0 bearer. Access is revoked by deleting the Motive connector or app in Claude or ChatGPT, which invalidates it immediately.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Reaching fleet data from an assistant
Connect the official connector rather than working through the API by hand.
02
Cutting access
Delete the connector in Claude or ChatGPT; it is invalidated immediately.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- a Motive fleet admin account, signed in over OAuth 2.0
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.us.gomotive.com/mcpRequirements
- OAuth 2.0 (Bearer token)
