TomTom MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAPS | No | Optional backend to use. Set to 'ORBIS' to use Orbis APIs instead of Genesis APIs | |
| TOMTOM_API_KEY | Yes | Your TomTom API key obtained from the TomTom Developer Portal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tomtom-get-api-keyA | Internal tool for apps to retrieve the TomTom API key |
| tomtom-get-app-configA | Internal tool for apps to retrieve client configuration such as the attribution user-agent |
| tomtom-get-viz-dataA | Internal tool for apps to retrieve cached visualization data by viz_id |
| tomtom-geocodeA | Convert street addresses to coordinates (does not support points of interest) |
| tomtom-reverse-geocodeA | Convert coordinates to addresses |
| tomtom-fuzzy-searchB | Typo-tolerant search for addresses, points of interest, and geographies |
| tomtom-poi-searchC | Find specific business categories |
| tomtom-nearbyC | Discover services within a radius |
| tomtom-routingA | Calculate optimal routes between two locations. The primary tool for directions, routes, travel time, or distance between places (e.g. 'route from Amsterdam to Berlin', 'how long to drive from A to B'). Returns turn-by-turn directions, distance, travel time, and a map image. Multi-stop routes with 3+ waypoints are handled by tomtom-waypoint-routing; visualizing multiple routes or combining routes with markers/polygons on a single map image is handled by tomtom-dynamic-map. |
| tomtom-waypoint-routingA | Plan multi-stop routes through 3 or more waypoints. Use when the user needs to visit multiple locations in sequence (e.g. 'route from A to B via C and D'). Returns optimized turn-by-turn directions, total distance, and travel time. For simple A-to-B routes, use tomtom-routing instead. |
| tomtom-reachable-rangeB | Determine the area reachable within a specified time or driving distance |
| tomtom-trafficA | Find and display traffic incidents in an area. The primary tool for questions about traffic, accidents, road closures, congestion, or dangerous road conditions. Returns detailed incident data including severity, description, delay, and affected roads. Provides complete traffic incident data on its own; plotting incidents as markers with tomtom-dynamic-map is not needed. |
| tomtom-static-mapB | Generate custom map images from TomTom Maps with specified center coordinates, zoom levels, and style options |
| tomtom-dynamic-mapA | Render a custom map image with markers, drawn lines, polygons, and area overlays using server-side rendering. Intended for map visualization: showing locations on a map, highlighting areas, or combining multiple visual elements in one view. Not intended for route calculations (tomtom-routing) or traffic incidents (tomtom-traffic). The optional routePlans parameter can calculate and draw routes on the map; it is meant for routes combined with other map elements (markers, polygons) in a single image. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools are clearly separated by purpose, with routing vs. waypoint-routing and static-map vs. dynamic-map explicitly disambiguated. Some overlap exists among fuzzy-search, geocode, and poi-search, but the descriptions provide enough contextual boundaries to guide correct selection.
All tools share a consistent tomtom- prefix and lowercase hyphenated style, which makes the set predictable. Verb forms vary across geocode, search, routing, and nearby, so it is not a strict verb_noun pattern, but the deviations are minor and readable.
Fourteen tools is within the ideal scope for a mapping, search, routing, traffic, and visualization server. Each tool covers a distinct operational area, and the three internal tools serve a clear supporting role for apps using the server.
The server provides strong coverage of the core mapping domain: forward and reverse geocoding, fuzzy and category search, nearby discovery, simple and multi-stop routing, reachable range, traffic, and map rendering. There are no obvious dead ends for typical user requests involving locations, directions, traffic, or map images.