The Geotab MCP server is the fleet-telematics implementation of the Model Context Protocol (MCP) — an open standard that lets AI assistants discover and call external tools dynamically. It exposes MyGeotab as AI-callable tools, so any MCP-compatible client — such as Claude, ChatGPT, Microsoft Copilot Studio, Cursor, or VS Code — can query and act on your fleet data in natural language. No SQL, no API code, and no manual report exports are required.
Your AI assistant acts as the front end, the Geotab MCP server acts as the secure bridge to your fleet database, and your MyGeotab account remains the authoritative source of truth. The server runs on Geotab infrastructure, authenticates through Geotab Unified Login, and executes every request under your own MyGeotab identity and clearances.
The server is available at https://mcp.geotab.com/mygeotab and is included with the GO Plan subscription at no additional cost.
Prerequisite: your MyGeotab user must be migrated to Geotab Unified Login before you can connect. See Getting started for the steps.
The MCP server exposes the same data model as the MyGeotab API, organized into AI-discoverable tools. It currently provides roughly 20 tools spanning more than 50 MyGeotab entity types, with token-optimized tool descriptions, structured errors, and multi-call orchestration support. Coverage includes:
Device, DeviceStatusInfo, Trailer, TrailerAttachmentUser, Group, SecurityClearance, and driver lookupsTrip, LogRecord, DriverChange, posted-road-speed comparisonsFaultData, StatusData, fault dismissal, VIN decodingDutyStatusLog, DutyStatusAvailability, DVIRLog, HOS rule setsFuelTransaction, EVStatusInfo, BatteryStateOfHealth, emission enrollmentZone and Route entitiesSendReportProcessingRequest and GetAceResults for natural-language insights powered by Geotab AceSpecialized tools include DecodeVins, GetHosRuleSets, GetPostedRoadSpeedsForDevice, DismissFaults, EmissionEnrollDevices, and GetEmissionComplianceDeadline. Use ListEntities from any connected client to see the full set of supported entities for your database.
Common workflows include:
GetAceResults.Once connected, you can ask your AI assistant questions like these in plain language. Use them as starting points and adapt them to your fleet.
New to MCP? The Getting started with MyGeotab MCP guide on the Geotab Support site walks you through connecting your first client step by step.
Using SAML single sign-on? SAML-authenticated MyGeotab accounts cannot connect directly. Use a Basic Authentication account migrated to Unified Login for MCP access, or contact your Geotab account team about migrating your database.
Server URL: https://mcp.geotab.com/mygeotab Transport: Streamable HTTP Auth: OAuth 2.1 with PKCE (secure browser sign-in; no credentials stored) Default DB: my.geotab.com (override per request if needed)
Most MCP-compatible clients have a Connectors or MCP serverssettings panel. Add a new custom server and paste the URL above. On first use, the client redirects you to Geotab's sign-in page; after you authenticate, the client receives a scoped token and the connection is authorized. Your MyGeotab password is never entered into or stored by the AI client.
Open Settings → Connectors → Add custom connector and paste https://mcp.geotab.com/mygeotab. Claude prompts for Geotab authorization on first query. On Team and Enterprise plans, only administrators can add connectors.
Edit claude_desktop_config.json (typically at ~/.config/claude/claude_desktop_config.json on macOS/Linux or %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"geotab": {
"url": "https://mcp.geotab.com/mygeotab"
}
}
}In ChatGPT, open Settings → Connectors → Add custom connector (available on Plus, Pro, Business, and Enterprise plans with developer mode enabled). Provide the following:
https://mcp.geotab.com/mygeotabSave the connector, then enable it inside a chat by selecting it from the connector picker. ChatGPT prompts for Geotab authorization on first use.
Add the Geotab MCP server as a custom connector / tool, using the URL https://mcp.geotab.com/mygeotab and OAuth authentication. Agents in Copilot Studio can then call MyGeotab tools directly.
In Cursor, open Settings → MCP → Add custom MCP server. Cursor opens an mcp.json file where you add the server configuration:
{
"mcpServers": {
"MyGeotab": {
"url": "https://mcp.geotab.com/mygeotab"
}
}
}Cursor separates Home MCP servers (for local development) from Cloud MCP servers (for remote use). Add the configuration under whichever fits your workflow — or under both if you want the connection available in each context.
Add the following to .vscode/mcp.json:
{
"servers": {
"geotab": {
"url": "https://mcp.geotab.com/mygeotab"
}
}
}Once connected, confirm everything works with a quick question such as "How many vehicles do I have in MyGeotab?" — then explore the example prompts for more ideas.
The MCP server authenticates through Geotab Unified Login using OAuth 2.1 with PKCE. On first connection, your AI client redirects you to Geotab's sign-in page; after you authenticate, the client receives a scoped token that the MCP server validates on every request. Your AI client never sees your MyGeotab password.
All API calls execute under your MyGeotab user identity and clearances — the MCP server cannot return data your account is not authorized to view.
Disconnect the server from your AI client to immediately stop new requests. You can also revoke access through your Geotab Unified Login account settings.
The following are intentionally not exposed:
Authenticate and SetUserPassword are not callable via MCP — authentication is handled by the Unified Login flow.Remove is blocked for Device, User, Group, FuelTransaction, Trailer, TrailerAttachment, MediaFile, and TextMessage to protect against accidental data loss.For mission-critical or high-volume integrations that fall outside the MCP scope, use the MyGeotab SDK directly.
Any client that implements the Model Context Protocol — including Claude (Web, Desktop, Team, Enterprise), ChatGPT, Microsoft Copilot Studio, Cursor, VS Code with GitHub Copilot, and custom agents built with an MCP SDK. If your client supports adding a custom Streamable HTTP server, it should work. Support for Google Gemini is planned.
MCP access is included with the GO Plan subscription at no additional cost.
The same data model as the MyGeotab API — devices, drivers, trips, zones, HOS, DVIR, exceptions, faults, fuel, EV status, audit logs, and more. Access is scoped to your account's clearances.
An active MyGeotab account with API access, and a user migrated to Geotab Unified Login. Most users can self-migrate from their MyGeotab profile page. If your account uses SAML single sign-on, use a Basic Authentication account migrated to Unified Login, or contact your Geotab account team.
Contact your Geotab account team or post in the Geotab Developer Community.
The MyGeotab MCP user guide is the best place to start — it covers setup, supported clients, and troubleshooting in detail.