LABSCO SUMMARY

Location questions answered with data, and a picture to go with it.

The useful pairing here is search plus routing plus rendering: an agent can resolve a vague place name, plan the multi-stop route, check what traffic is doing on it, and return an actual map image with the route drawn — rather than a list of coordinates the reader has to plot themselves. The hosted endpoint means the only thing you manage is the key.

What it is

TomTom's Maps MCP server: addresses to coordinates and back, place search, route calculation, traffic incidents and map images, wrapped as tools. It runs locally over stdio or as a hosted endpoint TomTom operates, and can be pointed at either the TomTom Maps or the TomTom Orbis Maps backend.

What you get

Geocoding both directions — tomtom-geocode for address to coordinates, tomtom-reverse-geocode for coordinates to address
Search shaped to the question: tomtom-fuzzy-search tolerates typos, tomtom-poi-search targets business categories, tomtom-nearby sweeps a radius
Routing that goes past A to B — tomtom-routing, tomtom-waypoint-routing for multi-stop planning, tomtom-reachable-range for what is reachable inside a time or distance budget
tomtom-traffic for real-time incident data on the roads in question
Map images the model can hand back: tomtom-static-map for a plain image, tomtom-dynamic-map for stitched tiles with markers, routes and overlays rendered server-side and returned as base64 PNG
Switching to the Orbis backend adds tomtom-ev-routing with charging stops, tomtom-search-along-route, tomtom-area-search, tomtom-ev-search and tomtom-data-viz; tomtom-static-map is only on the default backend

Requirements

A TomTom API key, created in the developer portal with all available APIs selected. The hosted server needs nothing installed — add an http entry for https://mcp.tomtom.com/maps and pass the key in a tomtom-api-key header, with an optional tomtom-maps-backend header choosing the backend; it is in public preview and the key must have MCP Server access enabled. Locally it is Node.js 22.x and the npm package @tomtom-org/tomtom-mcp, launched with npx, reading TOMTOM_API_KEY from the environment or a .env file. MAPS pins the backend at startup, and pinning it makes the per-request header inert. A published Docker image serves the same thing in HTTP mode on port 3000. Orbis and some EV features are themselves in public preview, so a 403 saying missing permissions usually means the account lacks that preview rather than that the call was wrong.

Setup effort

One command plus a key — npx @tomtom-org/tomtom-mcp@latest, then supply credentials

See installation options

USE CASES

01

Planning a multi-stop trip and showing it

Resolve each stop to coordinates, route through them in order, then render the route onto a map image.

tomtom-geocodetomtom-waypoint-routingtomtom-dynamic-map

02

Working out how far someone can get from here

Compute the reachable area for a time or distance budget, then look for the places that fall inside it.

tomtom-reachable-rangetomtom-poi-search

03

Deciding whether to leave now

Calculate the route and read the current incidents affecting it.

tomtom-routingtomtom-traffic

04

Turning a half-remembered place name into an address

Search with typo tolerance, then reverse-geocode the coordinates you picked to get the postal address back.

tomtom-fuzzy-searchtomtom-reverse-geocode

14 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`tomtom-dynamic-map`

Render a custom map image with markers, drawn lines, polygons, and area overlays using server-side rendering. Use this for MAP VISUALIZATION: showing locations on a map, highlighting areas, or combining multiple visual elements in one view. Do NOT use this for: route calculations (use tomtom-routing), or traffic incidents (use tomtom-traffic). The optional routePlans parameter can calculate and draw routes on the map, but only use it when you need routes combined with other map elements (markers, polygons) in a single image.

BEFORE YOU INSTALL

What to know first

Tools you get

14 tools when we connected; the project documents 19. Three of the 14 are undocumented helpers for the bundled app host. MAPS=tomtom-orbis-maps adds tomtom-ev-routing, tomtom-search-along-route, tomtom-area-search, tomtom-ev-search and tomtom-data-viz but drops tomtom-static-map, so no single setup has all 19.

Requires

npx on PATH
Node.js 22.x
TOMTOM_API_KEY in your environment

INSTALLATION

Connect your client

Server setup

npx

TERMINAL

npx @tomtom-org/tomtom-mcp@latest

Hosted endpoint

ENDPOINT URL

https://mcp.tomtom.com/maps

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

Claude Desktop, Cursor, Windsurf

JSON

{
  "mcpServers": {
    "tomtom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tomtom-org/tomtom-mcp@latest"
      ],
      "env": {
        "TOMTOM_API_KEY": "<YOUR_TOMTOM_API_KEY>"
      }
    }
  }
}

VS Code

VS CODE · JSON

{
  "servers": {
    "tomtom-mcp": {
      "type": "http",
      "url": "https://mcp.tomtom.com/maps",
      "headers": {
        "tomtom-api-key": "<YOUR_TOMTOM_API_KEY>"
      }
    }
  }
}

smolagents

Install smolagents with MCP support:

SMOLAGENTS · TERMINAL

pip install 'smolagents[mcp]'

Run the TomTom Maps MCP server in HTTP mode:

SMOLAGENTS · TERMINAL

docker run -d -p 3000:3000 ghcr.io/tomtom-international/tomtom-maps-mcp:latest

Connect to it from your Python script, with your TomTom API key in the header:

SMOLAGENTS

from smolagents import ToolCollection

# Connect to the MCP server running on localhost:3000
with ToolCollection.from_mcp(
    {"url": "http://localhost:3000/mcp",
     "headers": {"tomtom-api-key": "<YOUR_TOMTOM_API_KEY>"},
     "transport": "streamable-http"},
    trust_remote_code=True
) as collection:
    # List all available tools
    for tool in collection.tools:
        print(tool.name)

TomTom MCP

Location questions answered with data, and a picture to go with it.

What it is

What you get

Requirements

Setup effort

Planning a multi-stop trip and showing it

Working out how far someone can get from here

Deciding whether to leave now

Turning a half-remembered place name into an address

14 tools

`tomtom-dynamic-map`

`tomtom-fuzzy-search`

`tomtom-geocode`

`tomtom-get-api-key`

`tomtom-get-app-config`

`tomtom-get-viz-data`

`tomtom-nearby`

`tomtom-poi-search`

`tomtom-reachable-range`

`tomtom-reverse-geocode`

`tomtom-routing`

`tomtom-static-map`

`tomtom-traffic`

`tomtom-waypoint-routing`

What to know first

Tools you get

Requires

Connect your client

Server setup

npx

Hosted endpoint

MCP Clients

Claude Desktop, Cursor, Windsurf

VS Code

smolagents

TomTom MCP

Location questions answered with data, and a picture to go with it.

What it is

What you get

Requirements

Setup effort

Planning a multi-stop trip and showing it

Working out how far someone can get from here

Deciding whether to leave now

Turning a half-remembered place name into an address

14 tools

tomtom-dynamic-map

tomtom-fuzzy-search

tomtom-geocode

tomtom-get-api-key

tomtom-get-app-config

tomtom-get-viz-data

tomtom-nearby

tomtom-poi-search

tomtom-reachable-range

tomtom-reverse-geocode

tomtom-routing

tomtom-static-map

tomtom-traffic

tomtom-waypoint-routing

What to know first

Tools you get

Requires

Connect your client

Server setup

npx

Hosted endpoint

MCP Clients

Claude Desktop, Cursor, Windsurf

VS Code

smolagents

Same category

Gaode Map Location & POI

EdgeOne Geo Location

MCP Location Services for LLM

QGIS

`tomtom-dynamic-map`

`tomtom-fuzzy-search`

`tomtom-geocode`

`tomtom-get-api-key`

`tomtom-get-app-config`

`tomtom-get-viz-data`

`tomtom-nearby`

`tomtom-poi-search`

`tomtom-reachable-range`

`tomtom-reverse-geocode`

`tomtom-routing`

`tomtom-static-map`

`tomtom-traffic`

`tomtom-waypoint-routing`