TomTom Maps MCP Server

Available tools

Available tools

The TomTom Maps Remote MCP Server is in public preview.

Every tool runs on TomTom Orbis Maps, for both the Remote MCP Server and the local setup.

In clients that support MCP Apps, tool results also appear on an interactive map. See Interactive maps for details.

Search & geocoding

Routing

  • tomtom-routing: Calculate a route through an origin, optional stops and a destination, with distance, travel time and traffic delay

Traffic

Maps & data visualization

These tools draw their map in the client through an MCP App, so they need a client that supports MCP Apps.

  • tomtom-dynamic-map: Interactive map with custom markers, routes and polygons

  • tomtom-data-viz: Visualize your own GeoJSON data on an interactive TomTom basemap. Supports markers, heatmaps, clusters, lines, polygon fills and choropleth maps

Getting geometry from a tool response

Tools that return TomTom data accept a response_detail parameter. By default (compact) they return the essential fields and the coordinates of each place, but no route lines, incident locations or search areas, so a response doesn’t use up the model’s context.

tomtom-routing, tomtom-traffic, tomtom-area-search and tomtom-search-along-route also accept geometry.

ValueReturns
compact (default)Essential fields and the coordinates of each place. No route lines, incident locations or search areas.
geometrycompact, plus a geometry key holding route lines, incident locations and search areas as a GeoJSON FeatureCollection, simplified to at most 1,000 points per feature.
fullThe raw API response. Lossless, but many times larger.

Use geometry when you need the coordinates themselves, for example to draw the result on your own map. For an Amsterdam to Berlin route, geometry is about 22 KB and full about 210 KB. See the GitHub repository for the format.

Release notes

The release notes on GitHub list the changes in each version, with migration steps for breaking changes.