← Back to directory

TomTom Maps MCP Server

Official

TomTom location, search, routing, and traffic data for AI workflows.

GitHub source repository ↗

★ 53 Stars Category · Other Popular Source revision 39ab5f123e24

63FMRS · C

Reliability

10/20

Security and permissions

12/20

Maintenance

12/20

Documentation

15/20

Setup experience

14/20

An official TomTom-maintained MCP server covering geocoding, search, routing, traffic, and map rendering, with remote HTTP, local stdio, local HTTP, and Docker usage options. A TomTom API key is required, while Orbis and EV capabilities have preview and access limitations.

Read the FMRS scoring method →

TomTom Maps MCP Server is maintained by TomTom and provides AI agents and development environments with location services, geocoding, search, routing, traffic data, and static map capabilities. It supports the standard TomTom Maps backend and the optional TomTom Orbis Maps backend.

Tools

tomtom-geocode

Converts addresses into coordinates.

tomtom-reverse-geocode

Converts GPS coordinates into addresses.

tomtom-fuzzy-search

Provides intelligent search with typo tolerance.

tomtom-poi-search

Finds points of interest and businesses by category.

tomtom-nearby

Discovers services or places within a radius.

tomtom-routing

Calculates optimal routes between locations.

tomtom-waypoint-routing

Plans routes with multiple stops.

tomtom-reachable-range

Calculates reachable areas using a time or distance budget.

tomtom-traffic

Provides real-time traffic incident data.

tomtom-static-map

Generates custom map images.

tomtom-dynamic-map

Renders maps with custom markers, routes, and traffic visualization.

tomtom-ev-routing

Plans long-distance EV routes with automatic charging-stop optimization.

tomtom-search-along-route

Finds points of interest such as restaurants, gas stations, and hotels along a route.

tomtom-area-search

Searches for places within a circle, polygon, or bounding-box area.

tomtom-ev-search

Finds EV charging stations with real-time availability and connector types.

tomtom-data-viz

Visualizes custom GeoJSON data on a TomTom basemap using markers, heatmaps, clusters, and choropleths.

Setup

The remote preview server requires no local installation: replace TOMTOM_API_KEY with a valid key and add the configuration to an MCP client that supports custom HTTP headers. Alternatively, use Node.js 22.x to install with npm or run @tomtom-org/tomtom-mcp@latest with npx. For local HTTP or Docker deployments, provide the key in the tomtom-api-key request header.

claude_desktop_config.json

{"mcpServers":{"tomtom-mcp":{"type":"http","url":"https://mcp.tomtom.com/maps","headers":{"tomtom-api-key":"your_api_key_here"}}}}

Generate and validate client config

Fit and risk

Best for

AI agents needing global geocoding, place search, routing, and traffic data
Developers integrating TomTom mapping capabilities with Claude Desktop, VS Code, Cursor, or Windsurf
Applications that need HTTP or Docker-based map-service integration

Not for

Applications that do not need TomTom location or navigation data
Users who cannot provide a TomTom API key
Offline mapping or offline API-data scenarios

Required permissions

Requires a valid TomTom API key.
The key must have MCP Server access enabled; local tests call real APIs and consume API quota.
TomTom Orbis Maps and some EV features may require additional account access.

Risks and side effects

The MCP client or operator is responsible for updates, patches, and security configuration of local deployments.
API calls consume quota.
TomTom Orbis Maps and some EV features are in public preview and may produce 403 errors or be unavailable to some accounts.
Map and traffic results depend on TomTom services and the selected backend.

Troubleshooting

Verify that TOMTOM_API_KEY is set and has the required API permissions.
For 403 errors, select all available products for the key in the TomTom Developer Portal; if the issue remains, use the tomtom-maps backend.
HTTP mode requires the key in the tomtom-api-key header.
In dual-backend mode, use tomtom-maps-backend to select the backend; if MAPS is set at startup, that header is ignored.
Before local testing, confirm that .env exists and remember that tests make real API requests.

Use cases

Address and coordinate conversion

Place, POI, and nearby-service search

Point-to-point and multi-stop routing

Traffic incident lookup

Static and dynamic map image generation

EV routing and charging-station search with the Orbis backend

Supported clients

Claude DesktopFull support

VS Code (GitHub Copilot)Full support

CursorFull support

WindsurfFull support

SmolagentsPartial support

Related MCP servers

Compare with other MCP servers