MyGeotab MCP
by MyGeotab MCP
Query and change a MyGeotab fleet database from an AI agent. Six of the 20 tools are generic dispatchers — Get, Add, Set and Remove take an entity type as an argument and reach 51+ MyGeotab entity types, so the tool count understates the surface. OAuth 2.1 with PKCE, identity-only scopes.
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.
Connect MyGeotab MCP via MCP
https://mcp.geotab.com/mygeotabWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
MyGeotab MCP Tools & Capabilities (20)
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
ListEntitiesfrom 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,profileandemail. 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.
UploadMediaFileandDownloadMediaFileappear in the directory listing and appear in Geotab's "Blocked for now" table. GetAceResultsruns 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)andRoute (Add)as failing or needing an undocumented field;ZoneandDistributionListupdates require a full entity fetch first;AddIn (Add)needs a signed Geotab manifest; andGetAceResults"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
Getper minute onLogRecord, 100Setper minute onExceptionEvent. - 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
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.
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.
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.
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.
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.
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.
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.
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
- Geotab MCP server developer documentation (retrieved 2026-08-23).
llms.txt,llms-full.txtand the.mdsuffix all returned 404 on this host; the nominated URL was the winning route. · retrieved 2026-08-23 - Getting started with MyGeotab MCP, Geotab Support Center (retrieved 2026-08-23) · retrieved 2026-08-23
- MyGeotab MCP limitations and support, Geotab Support Center (retrieved 2026-08-23). Source of the blocked-method table. · retrieved 2026-08-23
- MyGeotab Model Context overview, Geotab Support Center (retrieved 2026-08-23) · retrieved 2026-08-23
- Geotab Ace agent model card (retrieved 2026-08-23; the extensionless path 301s here). Source of the Ace architecture, data sources and driver-risk claims. · retrieved 2026-08-23
- MyGeotab API reference entity definitions — · · · · · · · (retrieved 2026-08-23; each extensionless path 301s to its
index.html). Field lists on these pages are rendered client-side; we read them from the Next.js RSC flight payload in the same response. · retrieved 2026-08-23 - Restricted Data Mode, Geotab Support Center (retrieved 2026-08-23) · retrieved 2026-08-23
- Data access, Geotab Support Center (retrieved 2026-08-23) · retrieved 2026-08-23
- Geotab MCP Connector product overview (retrieved 2026-08-23) · retrieved 2026-08-23
- Live auth posture check: anonymous
initializetohttps://mcp.geotab.com/mygeotabreturned HTTP 401 with an OAuth bearer challenge; RFC 9728 metadata athttps://mcp.geotab.com/.well-known/oauth-protected-resource/mygeotaband authorization server metadata athttps://mcp.geotab.com/.well-known/oauth-authorization-server(2026-08-23). A control probe at a nonexistent resource path returned 404, so the descriptor is genuine rather than a catch-all. · retrieved 2026-08-23 - Both
developers.geotab.com/robots.txtandsupport.geotab.com/robots.txtallow the paths read here; neither carries aContent-Signaldirective (retrieved 2026-08-23). · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Geotab support — <mailto:support@geotab.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- MyGeotab MCP
- Tools
- 20
- Domain
- mcp.geotab.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.