What features does TomTom-MCP MCP server provide?

Q: What features does TomTom-MCP MCP server provide?

Geocoding & Reverse Geocoding: Access global geocoding and reverse geocoding via the tomtom-geocode and tomtom-reverse-geocode tools.. Fuzzy Search & POI Search: Intelligent search with typo tolerance and points-of-interest search across TomTom datasets.. Nearby Search: Discover services and POIs within a specified radius, enabling proximity-based queries.. Routing & Waypoint Routing: Calculate optimal routes between locations and support multi-stop routing for complex itineraries.. Reachable Range & Traffic: Determine coverage areas by time/distance budgets and access real-time traffic data.. Static & Dynamic Map Rendering: Generate custom static map images and render dynamic map layers server-side using MapLibre Native.. Optional Orbis Maps Backend: Switch between TomTom Maps and TomTom Orbis Maps backends using the MAPS environment variable.. Deployment Modes & API Key Security: Run in stdio or HTTP mode and deploy via Docker/Docker Compose; API key can be supplied via .env, env var, or HTTP header.

TomTom-MCP MCP Server 2025: Features & Setup Guide

Overview

The TomTom MCP Server consolidates access to TomTom's location services into a programmable, self-contained Node.js server. It exposes a suite of MCP tools (tomtom-geocode, tomtom-reverse-geocode, tomtom-fuzzy-search, tomtom-poi-search, tomtom-nearby, tomtom-routing, tomtom-waypoint-routing, tomtom-reachable-range, tomtom-traffic, tomtom-static-map, tomtom-dynamic-map) via a JSON-RPC/HTTP interface, enabling AI workflows and development environments to query TomTom data without bespoke integration. It supports two backends: TomTom Maps (GENESIS) by default and TomTom Orbis Maps (MAPS=orbis). Deployment is flexible: run in stdio mode for AI assistants, via HTTP mode for web apps, or in Docker and Docker Compose configurations. A TomTom API key is required and can be supplied via a .env file, environment variable, or in the tomtom-api-key header when using HTTP. The dynamic map tool is optional and requires Node.js 22.x and the MapLibre Native dependencies; when enabled, it renders map layers server-side and returns PNGs as Base64 strings. The README provides integration guides for Claude, VS Code, Cursor AI, Windsurf, and Smolagents, illustrating how to connect the MCP server to diverse AI tools.

Features

Geocoding & Reverse Geocoding

Access global geocoding and reverse geocoding via the tomtom-geocode and tomtom-reverse-geocode tools.

Fuzzy Search & POI Search

Intelligent search with typo tolerance and points-of-interest search across TomTom datasets.

Nearby Search

Discover services and POIs within a specified radius, enabling proximity-based queries.

Routing & Waypoint Routing

Calculate optimal routes between locations and support multi-stop routing for complex itineraries.

Reachable Range & Traffic

Determine coverage areas by time/distance budgets and access real-time traffic data.

Static & Dynamic Map Rendering

Generate custom static map images and render dynamic map layers server-side using MapLibre Native.

Optional Orbis Maps Backend

Switch between TomTom Maps and TomTom Orbis Maps backends using the MAPS environment variable.

Deployment Modes & API Key Security

Run in stdio or HTTP mode and deploy via Docker/Docker Compose; API key can be supplied via .env, env var, or HTTP header.