MyGeotab MCP

Query and change a MyGeotab fleet database from an AI agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the MyGeotab MCP connector does

The MyGeotab MCP server connects a Geotab fleet-telematics database to Claude, ChatGPT and any MCP-compatible agent. Anthropic lists 20 tools, but six take an entity type as an argument and reach more than 50 MyGeotab entity types — vehicles, trips, drivers, faults, zones and rules — to read, create, update and delete. Sign-in is OAuth 2.1 with PKCE.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

MyGeotab MCP tools (20)

  • Add
  • DecodeVins
  • DismissFaults
  • DownloadMediaFile
  • EmissionEnrollDevices
  • Get
  • GetAceResults
  • GetCountOf
  • GetDevicesInformation
  • GetEmissionComplianceDeadline
  • GetEntity
  • GetHosRuleSets
  • GetMediaUrl
  • GetPostedRoadSpeedsForDevice
  • ListEntities
  • Remove
  • SearchMedia
  • SendReportProcessingRequest
  • Set
  • SubmitFeedback
  • UploadMediaFile

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The tool count does not bound the surface. Six of the twenty tools are generic dispatchers over 51+ entity types. Any audit that reasons from the twenty names will understate what the connector can reach. Use ListEntities from a connected client to enumerate your own database's actual surface.
  • No application scopes exist. The RFC 9728 descriptor and the authorization server both advertise only openid, profile and email. Nothing at the OAuth grant separates reading a trip from removing a zone. The only boundary is the MyGeotab clearance on the account that signs in, which is a control an administrator sets inside MyGeotab and not one the consent screen offers.
  • This is worker-location data and your organisation is the controller for it. Geotab's privacy policy expressly does not apply where Geotab acts as a processor. Fleet telematics about identified employees is regulated as employee monitoring in the EU and in several other jurisdictions, and works-council or employee-representative consultation is commonly required before the monitoring changes. Connecting a general-purpose AI assistant to a driver-location database is a change to the processing, not a change to the tooling. Geotab publishes no MCP-specific works-council or employee-notice guidance that we could find, and we would treat its absence as a gap rather than as clearance.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-23, so no parameter-level detail is published here. In particular we cannot say which entity types each dispatcher accepts, or whether the server enforces the blocklist Geotab documents.
  • The two blocklists disagree. Geotab's developer page names eight Remove-blocked entity types; its support site names fifteen. Neither is a reliable statement of the boundary.
  • Anthropic lists two tools Geotab says are blocked. UploadMediaFile and DownloadMediaFile appear in the directory listing and appear in Geotab's "Blocked for now" table.
  • GetAceResults runs generated SQL. Geotab's Ace model card describes a sub-agent that writes SQL against your fleet warehouse and retries on error, and publishes accuracy metrics rather than accuracy guarantees. Verify anything material before acting on it.
  • Several documented capabilities are broken or gated. Geotab lists TextMessage (Add), TrailerAttachment (Add), MediaFile (Add) and Route (Add) as failing or needing an undocumented field; Zone and DistributionList updates require a full entity fetch first; AddIn (Add) needs a signed Geotab manifest; and GetAceResults "requires additional permissions".
  • Rate limits are MyGeotab's and pass through. Geotab states MyGeotab API rate limits apply and surface to the client as structured errors. Per-entity limits in its API reference vary widely — 1,000 Get per minute on LogRecord, 100 Set per minute on ExceptionEvent.
  • FedRAMP-authorized databases are not supported, and SAML SSO accounts cannot connect directly.
  • We did not observe whether a write actually reaches a vehicle. We ran no tool against this server. Every write claim on this page comes from Geotab's documentation and its published data model, not from a call we made.

Frequently asked questions

Can the MyGeotab MCP server see where an individual named driver is?

Yes. The DeviceStatusInfo entity carries Driver, Latitude, Longitude, Speed, Bearing and IsDriving in a single record, and Geotab documents it as the current state of a vehicle including bearing, location and speed. Trip and ExceptionEvent also carry a Driver field. The Driver record holds first name, last name, email login, phone number, employee number and licence number. So an ordinary Get call can return a named worker's position, speed and heading.

Can the MyGeotab connector send a message to a driver in a vehicle?

Geotab intends it to and documents the path as currently broken. The developer page lists text messages to drivers among the exposed capabilities, and TextMessage is an Add-supported entity whose IsDirectionToVehicle field controls whether it goes to the vehicle. Geotab's support site lists TextMessage (Add) as a known limitation with a serialization issue in messageContent and a workaround in progress. Treat it as a write path that is expected to work, not one that is withheld.

How many tools does the MyGeotab MCP server have?

Twenty is the tool count and a poor measure of the surface. Six of the twenty — Get, GetCountOf, GetEntity, ListEntities, Add, Set and Remove — take a MyGeotab entity type as an argument rather than naming one. Geotab states the server spans more than 50 entity types, and its support site says 51+. The reachable operation count is the entity count multiplied by the methods allowed on each, not twenty.

What OAuth permissions does the MyGeotab MCP server request?

Only identity claims. The server's RFC 9728 descriptor advertised scopes_supported of openid, profile and email on 2026-08-23, and its authorization server advertised the same three. None of them names a MyGeotab object or a verb. There is no way at consent to grant reading a trip without also granting Add, Set and Remove across every entity the account can reach.

Can the MyGeotab connector delete fleet data?

Yes, for entity types Geotab has not blocked. Remove is one of the twenty tools and Geotab's support site describes it as deleting entities by type, naming zones, rules, routes and distribution lists. Geotab blocks Remove for fifteen types including Device, User, Group, FuelTransaction, MediaFile and TextMessage. Everything outside that blocklist is deletable, and the blocklist is a vendor-side policy that can change.

What stops an AI agent from reading data the user should not see?

Your existing MyGeotab clearances, and nothing MCP-specific. Geotab states every API call executes under your MyGeotab user identity and clearances and that the server cannot return data your account is not authorized to view. The control is therefore the user's group-based data access in MyGeotab, configured by an administrator, not an MCP scope. A broadly cleared administrator account grants the agent that same breadth.

Does Geotab's privacy policy cover the driver data this connector reads?

No. Geotab's privacy policy states it applies where Geotab is the controller and does not apply where Geotab is a processor. Fleet records about your drivers are the processor case, so your organisation is the controller for them and carries the legal basis, the notice and any works-council or employee-consultation duty. Geotab defines controller and processor by reference to the EU General Data Protection Regulation.

How do I stop MyGeotab from recording a vehicle's GPS position?

Use Restricted Data Mode in MyGeotab, not an MCP setting. Geotab documents it as preventing MyGeotab from storing GPS coordinates and optionally GPS speed, and names personal driving in company vehicles as an intended use. It can be triggered by a rule, toggled manually, or set by the driver in the Drive app. Because it stops the data being stored, the connector cannot read what it excludes.

Sources

More Data & Research connectors

  • Airfield Directory

    Look up airfields, landing fees, fuel prices, pilot reports and METAR/TAF from an AI agent.

  • Airtable

    Read, write and restructure Airtable bases from your AI assistant.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put MyGeotab MCP to work.

Connect MyGeotab MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.