Get the FREE Ultimate OpenClaw Setup Guide →

tomtom

A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio tomtom-international-tomtom-mcp npx -y @tomtom-org/tomtom-mcp@latest \
  --env MAPS="tomtom-maps" \
  --env PORT="3000" \
  --env LOG_LEVEL="info" \
  --env TOMTOM_API_KEY="your_api_key"

How to use

The TomTom MCP Server exposes a set of geospatial tools that wrap TomTom APIs (such as geocoding, routing, search, traffic, and map generation) behind a single MCP interface. It supports both stdio mode (for AI assistants and local workflows) and HTTP mode (for web apps and API integrations). Tools like tomtom-geocode, tomtom-reverse-geocode, tomtom-routing, tomtom-traffic, and tomtom-static-map are available through the MCP server, enabling you to perform location-based queries, route calculations, and map rendering within client applications. To use it, configure your API key and preferred backend (maps or orbis-maps), then start the server in the desired mode and issue JSON-RPC style requests to access the included tools.

How to install

Prerequisites:

  • Node.js 22.x+ and npm (or pnpm/yarn as preferred)
  • TomTom API key with access to the required APIs

Installation steps:

  1. Install the MCP server via npm/npx:
npm install -g @tomtom-org/tomtom-mcp@latest

Or run directly without installing:

npx @tomtom-org/tomtom-mcp@latest
  1. Set up configuration and environment:
  • Obtain a TomTom API key from the TomTom Developer Portal.
  • Choose a backend: tomtom-maps (default) or tomtom-orbis-maps.
  1. Run in stdio mode (default for AI assistants):
npx @tomtom-org/tomtom-mcp@latest
  1. Run in HTTP mode (for web apps):
npm run build            # if you’re using the HTTP server workflow that requires a build step
npm run start:http
# or run the built binary directly (if provided by the distribution)
node bin/tomtom-mcp-http.js
  1. Alternatively, run via Docker as described in the README to host the server in a container.

Additional notes

Tips:

  • Always provide TOMTOM_API_KEY before starting the server. In HTTP mode, pass it via the tomtom-api-key header or set it in an environment variable.
  • The MAPS environment variable controls which backend is used at startup. If you set MAPS at startup, per-request header tomtom-maps-backend is ignored.
  • Default port is 3000; adjust PORT as needed. When running in HTTP mode, ensure your firewall or reverse proxy exposes port 3000.
  • For local development with verbose logging, set LOG_LEVEL=debug.
  • If you encounter API key issues, verify that the key has access to the required APIs and that it isn’t restricted by IP or referrer.

Related MCP Servers

Sponsor this space

Reach thousands of developers