The TomTom MCP Server provides seamless access to TomTom's location services for geospatial development and AI workflows.
Geocoding & Reverse Geocoding: Convert addresses to coordinates and coordinates to human-readable addresses with global coverage
Search & Discovery: Find points of interest using fuzzy search with typo tolerance, category-based POI search, and nearby services within a specified radius
Routing & Navigation: Calculate optimal routes between locations with multiple travel modes (car, pedestrian, bicycle, truck), plan multi-stop routes, and determine reachable areas by time/distance (isochrones)
Traffic Information: Access real-time traffic incident data within defined geographic areas
Map Visualization: Generate custom static map images and create advanced dynamic maps with custom markers, routes, and traffic visualization
Backend Flexibility: Choose between standard Genesis TomTom APIs or advanced Orbis backend (Public Preview) for enhanced features
AI Integration: Easily integrate into AI development environments like Claude Desktop, VS Code, Cursor AI, WindSurf, and Smolagents
Supports configuration through .env files for storing API keys and other configuration options.
Allows users to report issues, contribute code, and access documentation through the GitHub repository.
Runs as a Node.js application, enabling developers to incorporate TomTom's geospatial capabilities into Node.js-based AI workflows.
Provides access to TomTom's location services including geocoding, reverse geocoding, fuzzy search, POI search, nearby search, routing, waypoint routing, reachable range, traffic data, and static maps generation.
The TomTom MCP Server simplifies geospatial development by providing seamless access to TomTom’s location services, including search, routing, traffic and static maps data. It enables easy integration of precise and accurate geolocation data into AI workflows and development environments.
Node.js 22+
TomTom API key
How to obtain a TomTom API key:
Create a developer account on TomTom Developer Portal
Go to API & SDK Keys in the left-hand menu.
Click the red Create Key button.
Select all available APIs to ensure full access, assign a name to your key, and click Create.
For more details, visit the TomTom API Key Management Documentation.
Set your TomTom API key using one of the following methods:
Stdio Mode (Default - for AI assistants like Claude):
HTTP Mode (for web applications and API integration):
When running in HTTP mode, you need to include your API key in the Authorization header:
For example, to make a request using curl:
The Docker setup is also configured to use this HTTP mode with the same authentication method.
TomTom MCP Server can be easily integrated into various AI development environments and tools.
These guides help you integrate the MCP server with your tools and environments:
Claude Desktop Setup - Instructions for configuring Claude Desktop to work with TomTom MCP server
VS Code Setup - Setting up a development environment in Visual Studio Code
Cursor AI Integration - Guide for integrating TomTom MCP server with Cursor AI
WinSurf Integration - Instructions for configuring WindSurf to use TomTom MCP server
Smolagents Integration - Example showing how to connect Smolagents AI agents to TomTom MCP server.
By default the MCP tools use the Genesis TomTom APIs listed above. We also support using the "Orbis" backend for the same tools. To enable Orbis for all tools set the environment variable MAPS=ORBIS
Important: Orbis tools are currently in Public Preview and require explicit enablement for developer accounts. To request access, contact TomTom Sales:
Public Preview details: https://developer.tomtom.com/public-preview
Contact Sales to enable Orbis for your developer account
We fetch a Map Style JSON (either Genesis or Orbis), then use MapLibre (server-side) to:
add markers, routes, polygons and other layers defined by the style and request;
render all layers into an image using that style.
The server converts the rendered image to PNG and returns as Base64 string.
References:
Genesis Map Styles v2: https://developer.tomtom.com/map-display-api/documentation/mapstyles/map-styles-v2
Orbis style fetch: https://developer.tomtom.com/assets-api/documentation/tomtom-orbis-maps/styles-assets/fetch-style
⚠️ Important: All tests require a valid API key in .env as they make real API calls (not mocked). This will consume your API quota.
We welcome contributions to the TomTom MCP Server! Please see CONTRIBUTING.md for details on how to submit pull requests, report issues, and suggest improvements.
All contributions must adhere to our Code of Conduct and be signed-off according to the Developer Certificate of Origin (DCO).
Open issues on the GitHub repo
Please see our Security Policy for information on reporting security vulnerabilities and our security practices.
This project is licensed under the Apache License 2.0 - see the LICENSE.md file for details.
Copyright (C) 2025 TomTom NV
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Provides seamless access to TomTom's location services including search, routing, traffic and static maps data, enabling easy integration of precise geolocation data into AI workflows and development environments.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tomtom-international/tomtom-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server