TomTom Maps
by TomTom Maps
Geocode addresses, plan routes, find EV chargers and read live traffic from an AI agent. 15 read-only tools, no writes anywhere — but every call is a billed TomTom API transaction and no tool can check the bill.
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 TomTom Maps via MCP
https://mcp.tomtom.com/mapsWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
TomTom Maps Tools & Capabilities (15)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Every call is billed and nothing can check the bill. No tool in the surface reports usage, quota, balance or cost. Pair this connector with a free-tier key, or with a spend control set in the TomTom dashboard, before enabling blanket auto-approval.
- Overage behaviour is unverified. TomTom's pricing FAQ asks whether requests fail or get charged past the free allowance, and whether a spending cap can be set, but serves both answers through client-side script that our fetch could not read. We did not establish either answer.
- The advertised OAuth scopes gate nothing.
mcp:toolsandmcp:resourcesappear in the RFC 9728 descriptor and in no enforcement path in the source. - An invalid API key still handshakes. A key of thirty-one zeros produced a successful
initializeon 2026-08-22. Connection success does not mean the key works. - The documented default backend is wrong. TomTom's Quick Setup page says an absent
tomtom-maps-backendheader selects TomTom Maps; the hosted server selects Orbis. Set the header explicitly if the distinction matters to you. - Two documented tools are not on the hosted default.
tomtom-static-mapandtomtom-waypoint-routingexist only on the TomTom Maps backend, so Orbis users cannot generate a static map image or plan an explicitly multi-stop route by those names. - The remote server is in public preview, per a banner on every page of TomTom's MCP documentation. Behaviour and tool composition may change.
- Interactive maps need a client with MCP Apps support. TomTom names Claude Desktop as supporting them. Elsewhere the text results still arrive in full; only the visualisation is lost.
- Geocoding results may carry storage and caching restrictions. TomTom's developer terms are behind a sign-in wall at
docs.tomtom.com/legal/terms-and-conditions, which we did not attempt to bypass, so we could not verify what the licence permits. Commercial mapping licences commonly restrict retaining or re-publishing geocoded results, and TomTom's terms of use confirm some underlying data is ODbL-licensed with its own attribution obligations. Read the developer terms before storing anything this connector returns. - This is not TomTom's only MCP server. TomTom separately documents a Traffic Analytics MCP server with its own tools for junction, area and route analytics. Nothing on this page applies to it.
Frequently asked questions
Yes. TomTom's own documentation answers this in a comparison table row reading API Usage Charges: Yes, for both the remote and local server. Every tool call is a billed TomTom API transaction against your key. Each API carries a free monthly allowance — 20,000 geocoding requests, 2,500 routing requests — and usage beyond it is charged.
No. All 15 tools are reads, and the source confirms it: every registration in the repository sets readOnlyHint true and destructiveHint false. No tool creates, updates or deletes anything, because TomTom's mapping APIs return data rather than store it. The only thing a call changes is your metered usage total.
Fifteen are visible to the model, and the number depends on which map backend you select. The Orbis backend registers 15 tools; the older TomTom Maps backend registers 11, six of which differ. Three further tools exist in both modes but are marked app-only, so an assistant never sees or calls them.
Two named scopes, mcp:tools and mcp:resources, published in the server's RFC 9728 descriptor. Neither is enforced. We read the open-source code at version 1.6.7 and found the bearer-token check verifies only the issuer and signature, with no scope comparison anywhere in the request path.
Either works. The documented route is a TomTom API key sent in a `tomtom-api-key` header, which suits Claude Desktop and VS Code. The hosted endpoint also accepts an OAuth bearer token from TomTom's authorization server and exchanges it for a key behind the scenes. Sending neither returns HTTP 401.
Your key almost certainly lacks the right product entitlements. TomTom's setup guide instructs you to open API & SDK Keys, then tick All under Edit key or individually enable MCP Server, Map Display, Routing, Search, Geocoding, Reverse Geocoding and Traffic. A key missing any one of these fails only on the tools that need it.
Orbis, and the hosted server already defaults to it. Orbis is TomTom's current-generation platform and is the only backend offering EV routing, EV charger search, search-along-route, area search and data visualisation. It also renders interactive maps inside Claude Desktop. TomTom is deprecating parts of the older TomTom Maps platform.
Yes, one tool can. The tomtom-data-viz tool accepts a data_url parameter and the server fetches that HTTPS address itself, up to 50MB. The code blocks credentials in the URL, refuses any address resolving to a private IP, pins the resolved IP against DNS rebinding, and follows no redirects.
Sources
- TomTom Maps MCP Server documentation, Overview (retrieved 2026-08-22).
docs.tomtom.com/tomtom-mcp/documentation/overview, the URL named in the GitHub repository, redirects here. · retrieved 2026-08-22 - TomTom Maps MCP Server documentation, Available Tools (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom Maps MCP Server documentation, Remote vs. Local Setup (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom Maps MCP Server documentation, Quick Setup (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom Maps MCP Server documentation, Interactive Maps (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom Maps MCP Server documentation, Claude Desktop integration (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom pricing and free-tier allowances (retrieved 2026-08-22) · retrieved 2026-08-22
- TomTom Maps MCP server source, Apache 2.0, commit
39ab5f1, version 1.6.7 (read 2026-08-22). Tool registrations insrc/tools/, scope constant insrc/constants.ts, auth path insrc/indexHttp.tsandsrc/auth/jwtVerifier.ts, URL validation insrc/handlers/dataVizOrbisHandler.ts. · retrieved 2026-08-22 - npm package
@tomtom-org/tomtom-mcp1.6.7 (retrieved 2026-08-22) · retrieved 2026-08-22 - Live auth check: anonymous
initializereturning 401 with an RFC 9728 challenge, and the resource descriptor athttps://mcp.tomtom.com/.well-known/oauth-protected-resource/maps(2026-08-22).docs.tomtom.com/robots.txtexplicitly allows ClaudeBot, Claude-User and Claude-SearchBot. · retrieved 2026-08-22 - TomTom authorization server metadata (retrieved 2026-08-22) · retrieved 2026-08-22
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- TomTom support — · 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
- TomTom Maps
- Tools
- 15
- Domain
- mcp.tomtom.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.