TomTom Maps

Geocode addresses, plan routes, find EV chargers, read live traffic.

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 TomTom Maps connector does

The TomTom Maps MCP server gives Claude, ChatGPT and any MCP-compatible agent access to TomTom's geocoding, routing, EV-charging, traffic and map-rendering APIs. It exposes 15 tools, all read-only — nothing writes, updates or deletes. Sign-in is a TomTom API key in a tomtom-api-key header, or OAuth. Every call bills your TomTom account.

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.

TomTom Maps tools (15)

  • tomtom-geocode
  • tomtom-reverse-geocode
  • tomtom-fuzzy-search
  • tomtom-poi-search
  • tomtom-nearby
  • tomtom-poi-categories
  • tomtom-area-search
  • tomtom-ev-search
  • tomtom-search-along-route
  • tomtom-routing
  • tomtom-reachable-range
  • tomtom-ev-routing
  • tomtom-traffic
  • tomtom-dynamic-map
  • tomtom-data-viz

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:tools and mcp:resources appear 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 initialize on 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-backend header 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-map and tomtom-waypoint-routing exist 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

Does the TomTom MCP server cost money to use?

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.

Can the TomTom connector change anything in my account?

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.

How many tools does the TomTom Maps MCP server have?

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.

What OAuth permissions does the TomTom MCP server request?

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.

Do I need an API key or an OAuth login for TomTom MCP?

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.

Why do TomTom MCP tools return API key errors after connecting?

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.

Which TomTom backend should I choose, Maps or Orbis?

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.

Can the TomTom connector fetch data from a URL I give it?

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

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 TomTom Maps to work.

Connect TomTom Maps 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