icon for mcp server

TomTom

STDIOOfficial

MCP server providing TomTom geospatial services including search, routing, traffic and static maps

TomTom MCP Server

NPM Version License

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.

Demo

TomTom MCP Demo

Table of Contents


Security Notice

Keeping local deployments of the TomTom MCP Server up-to-date is the responsibility of the MCP client/operator. TomTom publishes updates to address known vulnerabilities, but failing to apply updates, patches, or recommended security configurations to your local instance may expose it to known vulnerabilities.

Quick Start

Prerequisites

  • Node.js 22.x (strict requirement for dynamic map tool, other tools may work with older/newer versions)
  • TomTom API key
  • OS-level dependencies for MapLibre GL Native:
    • macOS:
      # Install required dependencies via Homebrew brew install webp libuv webp icu4c jpeg-turbo glfw brew link icu4c --force
    • Ubuntu/Debian:
      # Install essential dependencies for MapLibre Native rendering sudo apt-get install -y libcurl4-openssl-dev libglfw3-dev libuv1-dev \ libicu-dev libpng-dev libjpeg-turbo8-dev libwebp-dev
    • Windows: Choose one of the two options:
      • Using Visual Studio:
      • Using MSYS2:
        • Install MSYS2, then run:
          pacman -S --needed mingw-w64-x86_64-angleproject mingw-w64-x86_64-curl-winssl \ mingw-w64-x86_64-glfw mingw-w64-x86_64-icu mingw-w64-x86_64-libjpeg-turbo \ mingw-w64-x86_64-libpng mingw-w64-x86_64-libwebp mingw-w64-x86_64-libuv

💡 Note: For any issues with native dependencies or the dynamic map tool, please refer to the Troubleshooting section.

How to obtain a TomTom API key:

  1. Create a developer account on TomTom Developer Portal and Sign-in
  2. Go to API & SDK Keys in the left-hand menu.
  3. Click the red Create Key button.
  4. 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.

Installation

npm install @tomtom-org/tomtom-mcp@latest # or run directly without installing npx @tomtom-org/tomtom-mcp@latest

Configuration

Set your TomTom API key using one of the following methods:

# 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 npx @tomtom-org/tomtom-mcp@latest

Environment Variables

VariableDescriptionDefault
TOMTOM_API_KEYYour TomTom API key-
MAPSBackend to use: GENESIS (default) or ORBISGENESIS
ENABLE_DYNAMIC_MAPSEnable or disable the dynamic maps featurefalse

Note about ENABLE_DYNAMIC_MAPS:

  • By default, the dynamic map tool is disabled (false) to avoid dependency issues
  • Set to true to enable dynamic maps after installing required dependencies
  • In Docker containers, this is set to true by default as all dependencies are pre-installed

Usage

Stdio Mode (Default - for AI assistants like Claude):

# Start MCP server via stdio npx @tomtom-org/tomtom-mcp@latest

HTTP Mode (for web applications and API integration):

npm run start:http # or after building the project node bin/tomtom-mcp-http.js

When running in HTTP mode, you need to include your API key in the tomtom-api-key header:

tomtom-api-key: <API_KEY>

For example, to make a request using curl:

curl --location 'http://localhost:3000/mcp' \ --header 'Accept: application/json,text/event-stream' \ --header 'tomtom-api-key: <API KEY>' \ --header 'Content-Type: application/json' \ --data '{ "method": "tools/call", "params": { "name": "tomtom-geocode", "arguments": { "query": "Amsterdam Central Station" } }, "jsonrpc": "2.0", "id": 24 }'

The Docker setup is also configured to use this HTTP mode with the same authentication method.

Docker Mode (recommended):

# Option 1: Using docker run directly # Note: Genesis is the default backend (same as npm package) docker run -p 3000:3000 ghcr.io/tomtom-international/tomtom-mcp:latest # To use Orbis backend instead of default Genesis: docker run -p 3000:3000 -e MAPS=orbis ghcr.io/tomtom-international/tomtom-mcp:latest # Option 2: Using Docker Compose (recommended for development) # Clone the repository first git clone https://github.com/tomtom-international/tomtom-mcp.git cd tomtom-mcp # Start the service (uses Genesis backend by default) docker compose up
curl --location 'http://localhost:3000/mcp' \ --header 'Accept: application/json,text/event-stream' \ --header 'tomtom-api-key: <API KEY>' \ --header 'Content-Type: application/json' \ --data '{ "method": "tools/call", "params": { "name": "tomtom-geocode", "arguments": { "query": "Amsterdam Central Station" } }, "jsonrpc": "2.0", "id": 24 }'

Integration Guides

  1. Connect via HTTP client: Send requests to http://localhost:3000/mcp with your API key in the tomtom-api-key header. 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:


Available Tools

ToolDescriptionDocumentation
tomtom-geocodeConvert addresses to coordinates with global coveragehttps://developer.tomtom.com/geocoding-api/documentation/geocode
tomtom-reverse-geocodeGet addresses from GPS coordinateshttps://developer.tomtom.com/reverse-geocoding-api/documentation/reverse-geocode
tomtom-fuzzy-searchIntelligent search with typo tolerancehttps://developer.tomtom.com/search-api/documentation/search-service/fuzzy-search
tomtom-poi-searchFind specific business categorieshttps://developer.tomtom.com/search-api/documentation/search-service/points-of-interest-search
tomtom-nearbyDiscover services within a radiushttps://developer.tomtom.com/search-api/documentation/search-service/nearby-search
tomtom-routingCalculate optimal routes between locationshttps://developer.tomtom.com/routing-api/documentation/tomtom-maps/calculate-route
tomtom-waypoint-routingMulti-stop route planning Routing APIhttps://developer.tomtom.com/routing-api/documentation/tomtom-maps/calculate-route
tomtom-reachable-rangeDetermine coverage areas by time/distancehttps://developer.tomtom.com/routing-api/documentation/tomtom-maps/calculate-reachable-range
tomtom-trafficReal-time incidents datahttps://developer.tomtom.com/traffic-api/documentation/traffic-incidents/traffic-incidents-service
tomtom-static-mapGenerate custom map imageshttps://developer.tomtom.com/map-display-api/documentation/raster/static-image
tomtom-dynamic-mapAdvanced map rendering with custom markers, routes, and traffic visualizationhttps://developer.tomtom.com/map-display-api/documentation/mapstyles/map-styles-v2

Orbis equivalents (optional backend)

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

ToolDescriptionOrbis API (documentation)
tomtom-geocodeForward geocoding: address → coordinateshttps://developer.tomtom.com/geocoding-api/documentation/tomtom-orbis-maps/geocode
tomtom-reverse-geocodeReverse geocoding: coordinates → addresshttps://developer.tomtom.com/reverse-geocoding-api/documentation/tomtom-orbis-maps/reverse-geocode
tomtom-fuzzy-searchGeneral search with typo tolerance and suggestionshttps://developer.tomtom.com/search-api/documentation/tomtom-orbis-maps/search-service/fuzzy-search
tomtom-poi-searchPoints of Interest (category-based) searchhttps://developer.tomtom.com/search-api/documentation/tomtom-orbis-maps/search-service/points-of-interest-search
tomtom-nearbyFind POIs near a coordinate within a radiushttps://developer.tomtom.com/search-api/documentation/tomtom-orbis-maps/search-service/nearby-search
tomtom-routingCalculate optimal route between two pointshttps://developer.tomtom.com/routing-api/documentation/tomtom-orbis-maps/calculate-route
tomtom-waypoint-routingMulti-stop / waypoint route planninghttps://developer.tomtom.com/routing-api/documentation/tomtom-orbis-maps/calculate-route
tomtom-reachable-rangeCompute coverage area by time or distance budgethttps://developer.tomtom.com/routing-api/documentation/tomtom-orbis-maps/calculate-reachable-range
tomtom-trafficTraffic incidents and related detailshttps://developer.tomtom.com/traffic-api/documentation/tomtom-orbis-maps/incident-details
tomtom-dynamic-mapAdvanced map rendering with custom markers, routes, and traffic visualizationhttps://developer.tomtom.com/assets-api/documentation/tomtom-orbis-maps/styles-assets/fetch-style

Important: Orbis tools are currently in Public Preview and require explicit enablement for developer accounts. To request access, contact TomTom Sales:

How dynamic map tool works

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:


Contributing & Local Development

Setup

git clone <repository> cd tomtom-mcp npm install cp .env.example .env # Add your API key in .env npm run build # Build TypeScript files node ./bin/tomtom-mcp.js # Start the MCP server

Testing

npm run build # Build TypeScript npm test # Run all tests npm run test:unit # Unit tests only npm run test:comprehensive # Integration tests

Testing Requirements

⚠️ Important: All tests require a valid API key in .env as they make real API calls (not mocked). This will consume your API quota.

Project Structure

src/
├── tools/             # MCP tool definitions
├── services/          # TomTom API wrappers
├── schemas/           # Validation schemas
├── utils/             # Utilities
└── createServer.ts    # MCP Server creation logic
└── index.ts           # Main entry point

Troubleshooting

Native Dependency Issues

If you encounter issues with native dependencies (especially for the dynamic map tool):

  1. Use Docker instead: Our Docker image includes all required dependencies pre-configured:

    docker run -p 3000:3000 ghcr.io/tomtom-international/tomtom-mcp:latest # or with Docker Compose (recommended for development) docker compose up
  2. Connect via HTTP client: Send requests to http://localhost:3000/mcp with your API key in the tomtom-api-key header.

This approach isolates all native dependencies inside the container while providing the same functionality.

Dynamic Map Tool Issues

By default, the dynamic map tool is disabled to avoid native dependency issues. To enable it:

  1. Ensure Node.js 22.x: The dynamic map tool specifically requires Node.js version 22.x
  2. Install required dependencies: Follow the platform-specific instructions in the Prerequisites section
  3. Enable dynamic maps: Set ENABLE_DYNAMIC_MAPS=true in your environment or .env file

For detailed build instructions, see the official MapLibre Native documentation:

API Key Issues

echo $TOMTOM_API_KEY # Check if set

Test Failures

ls -la .env # Verify .env exists cat .env # Check API key

Build Issues

npm run build # Rebuild npm cache clean --force # Clear cache

Contributing & Feedback

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

Security

Please see our Security Policy for information on reporting security vulnerabilities and our security practices.

License

This project is licensed under the Apache License 2.0 - see the LICENSE.md file for details.

Copyright (C) 2025 TomTom NV

Be the First to Experience MCP Now