TomTom

The TomTom MCP Server provides convenient, programmatic access to TomTom location services for geocoding, routing, traffic, and static map data, enabling seamless integration into AI workflows and development environments.

How to use

You run the MCP server and connect to it with an MCP client or HTTP requests. Use the STDIO mode for local AI integrations, or the HTTP mode for web applications and API clients. When operating in HTTP mode, supply your TomTom API key and choose a backend (TomTom Maps or TomTom Orbis Maps) as needed. The server executes the requested map and location services and returns results suitable for AI assistants, applications, or developers building geospatial features.

How to install

# Prerequisites
node -v
# Ensure Node.js 22.x is installed

# Install the MCP server
npm install @tomtom-org/tomtom-mcp@latest

# Or run directly without installing
npx @tomtom-org/tomtom-mcp@latest

Configuration and usage notes

Set your TomTom API key using one of these methods. The recommended approach is to use a .env file. You can also set an environment variable or pass the key on the command line when starting the server.

# Option 1: Use a .env file (recommended)
echo "TOMTOM_API_KEY=your_api_key" > .env

# Option 2: Environment variable
export TOMTOM_API_KEY=your_api_key

# Option 3: Pass as CLI argument
TOMTOM_API_KEY=your_api_key npx @tomtom-org/tomtom-mcp@latest

Mode options and endpoints

Stdio mode runs locally and is suitable for AI assistants and development workflows. HTTP mode exposes an HTTP API for web apps and services. When using HTTP mode, include your API key in the tomtom-api-key header. You may also specify a backend per request with the tomtom-maps-backend header if you start the server without a fixed MAPS setting.

Security considerations

Keep your MCP server up to date with security patches. When running locally, apply updates and follow best practices to minimize exposure. If you operate in production or share access, monitor access control and keys carefully.

Local development and testing

You can build and run the MCP server locally to test integrations with tools and clients. Use the standard Node.js tooling to install dependencies, build, and run. For UI debugging and testing, a debug UI is available that works with the HTTP mode.

Troubleshooting tips

Check that your API key is valid and present in the environment or headers. Verify that the MCP server is running in the expected mode (HTTP or STDIO) and that the endpoint URL is reachable when using HTTP. Review environment variable values if you encounter misconfigurations.

Notes on usage with Docker

You can run the MCP server in Docker and expose port 3000. By default, TomTom Maps is used as the backend. To switch to TomTom Orbis Maps, set the MAPS environment variable to tomtom-orbis-maps when starting the container.

Available tools

tomtom-geocode

Convert addresses to coordinates with global coverage

tomtom-reverse-geocode

Get addresses from GPS coordinates

tomtom-fuzzy-search

Intelligent search with typo tolerance

tomtom-poi-search

Find specific business categories

tomtom-nearby

Discover services within a radius

tomtom-routing

Calculate optimal routes between locations

tomtom-waypoint-routing

Multi-stop route planning

tomtom-reachable-range

Determine coverage areas by time/distance

tomtom-traffic

Real-time incidents data

tomtom-static-map

Generate custom map images

tomtom-dynamic-map

Advanced map rendering with custom markers, routes, and traffic visualization

tomtom-ev-routing

Plan long-distance EV routes with charging stop optimization

tomtom-search-along-route

Find POIs along a route

tomtom-area-search

Search for places within a geographic area

tomtom-ev-search

Find EV charging stations with availability

tomtom-data-viz

Visualize GeoJSON data on an interactive basemap