TomTom MCP Server for Geospatial APIs

Overview

The TomTom MCP Server is a lightweight proxy and adapter that exposes TomTom’s geospatial services (search, routing, traffic, static maps) through the Model Context Protocol (MCP). It lets AI agents, assistants, IDE extensions, and other MCP-aware clients call TomTom location APIs with a consistent tool/intent interface, while centralizing API key handling, rate-limiting headers, and optional map backend selection.

You can use TomTom’s hosted MCP endpoint (no installation) or run a local instance (Node.js) to integrate precise location lookups, route calculations with live traffic, POI search, and map images directly into AI workflows and developer tools.

Features

• Provide MCP-compatible endpoints for TomTom Search, Routing, Traffic, and Static Maps
• Hosted remote server (public preview) or local Node.js deployment
• Backend selection: TomTom Maps (default) or TomTom Orbis Maps
• Simple configuration via environment variables or client MCP config
• Debug UI for inspecting requests and responses (local runs)
• Meant for AI agents: compatible with VS Code MCP clients, Claude Desktop, GitHub Copilot workflows

Installation / Configuration

Prerequisites:

• Node.js 22.x (for local deployment)
• TomTom API key (create one at https://developer.tomtom.com/)

Install or run without installing:

# Install into a project
npm install @tomtom-org/tomtom-mcp@latest

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

Configuration options (environment variables):

Set your API key:

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

# Option 2: environment variable
export TOMTOM_API_KEY=your_api_key

# Option 3: inline when using npx
TOMTOM_API_KEY=your_api_key npx @tomtom-org/tomtom-mcp@latest

Sample local start:

# Start with custom port and map backend
PORT=4000 MAPS=tomtom-orbis-maps TOMTOM_API_KEY=your_api_key npx @tomtom-org/tomtom-mcp@latest

Remote MCP Server (no installation)

TomTom provides a hosted MCP endpoint (public preview):

Endpoint: https://mcp.tomtom.com/maps

Generic MCP client configuration example:

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

To choose backend add the header tomtom-maps-backend with value tomtom-maps or tomtom-orbis-maps. If omitted, tomtom-maps is used.

Available Tools / Resources

• Search tool: POI & address geocoding, reverse geocoding
• Routing tool: route planning with optional traffic-aware travel times
• Traffic tool: live traffic tiles and incidents
• Static Maps tool: generate map images (png/svg) for responses or previews
• Debug UI (local): inspect incoming MCP requests and the mapped TomTom API calls
• GitHub repo & source: https://github.com/tomtom-international/tomtom-mcp

Integration helpers:

• Example VS Code MCP config: place .vscode/mcp.json with the remote server entry
• Claude Desktop: configure MCP servers in escape hatch config files for macOS/Windows

Use Cases

• AI travel assistant: Combine POI search, routing and static maps to answer “Plan me a 2-stop driving route that avoids highways and shows ETA with current traffic.”
  • Steps: search POIs -> compute route -> render static map preview -> present ETA and instructions
• Location-aware code completions in IDE: Autocomplete addresses or insert map images into generated documentation using a VS Code MCP client
• Customer support bots: Reverse geocode a GPS point from user logs and return nearest service centers
• Fleet management prototypes: Query routing with traffic for ETA forecasts across multiple vehicles

Example MCP client snippet (JSON) to request a route via the remote server:

{
  "tool": "routing",
  "input": {
    "origin": {"lat": 52.370216, "lon": 4.895168},
    "destination": {"lat": 52.520008, "lon": 13.404954},
    "avoid": ["toll"],
    "traffic": true
  },
  "server": "tomtom-mcp"
}

Getting Help and Next Steps

• Try the hosted endpoint first to validate integration without running anything locally.
• For local development, run with LOG_LEVEL=debug to see detailed mapping of MCP requests to TomTom APIs.
• File issues or contribute via the project repo: https://github.com/tomtom-international/tomtom-mcp

Security note: keep local instances updated; TomTom publishes patches for vulnerabilities — apply updates and secure your deployment and API keys.