Interactive maps
Interactive maps
Instead of only getting text-based answers, your AI assistant can show location results on an interactive map, right inside your conversation. Search results appear as markers you can click, and the map draws routes and overlays live traffic.

Why interactive maps?
Traditional MCP tool responses return text: a list of coordinates, addresses or route details. Interactive maps enhance this by giving you a visual layer on top of every response:
- See results at a glance: Quickly understand spatial relationships instead of parsing coordinates
- Explore interactively: Pan, zoom and click markers to see details like place names, addresses and categories
- Share context visually: Maps make it easy to communicate location insights to stakeholders
There’s nothing extra to install or configure. The maps are built using MCP Apps and render automatically in supported AI clients.
How it works
- You ask your AI assistant a location-related question (for example, “Find coffee shops near the Eiffel Tower”).
- The assistant calls the appropriate TomTom tool (for example,
tomtom-nearby). - The tool returns both a text response with the results and an interactive map showing the locations visually.
The map appears inline in your conversation. You can pan, zoom and click on markers to see details, all without leaving your AI client.
Supported tools
These tools include interactive map visualizations:
Search & geocoding
| Tool | What the map shows |
|---|---|
| tomtom-geocode | Pinpoints the geocoded address on the map |
| tomtom-reverse-geocode | Shows the resolved address location for given coordinates |
| tomtom-fuzzy-search | Displays all matching results as markers with click-to-view details |
| tomtom-poi-search | Shows points of interest as markers with name and category info |
| tomtom-nearby | Plots nearby places within the search radius |
| tomtom-area-search | Shows the search area with the places found inside it |
| tomtom-search-along-route | Draws the route with the places found along it |
| tomtom-ev-search | Shows charging stations as markers with connector and power details |
Routing & navigation
| Tool | What the map shows |
|---|---|
| tomtom-routing | Draws the calculated route with markers for the origin, stops and destination |
Traffic & maps
| Tool | What the map shows |
|---|---|
| tomtom-traffic | Shows traffic incidents with live traffic flow overlay |
| tomtom-dynamic-map | Custom map with markers, routes, polygons and traffic layers |
| tomtom-data-viz | Your own GeoJSON data as markers, heatmaps, clusters, lines or choropleths |
For the full list of tools and API documentation links, see Available tools.
Map features
- Pan and zoom: Explore the map freely by dragging and scrolling
- Clickable markers: Click any marker to see place names, addresses and other details in a popup
- Automatic bounds: The map automatically adjusts its view to fit all results
- Traffic flow: Real-time traffic colors overlaid on roads (for traffic tools)
- Route lines: Clearly drawn route paths with start and end markers
- Theme toggle: Switch between light and dark map styles
Example
User prompt:
Find Italian restaurants within 1 km of Amsterdam Centraal station.What you get:
- A text response listing the restaurants with names, addresses and distances
- An interactive map centered on Amsterdam Centraal, with markers for each restaurant. Click any marker to see its details

Availability and client support
Interactive maps need an MCP client that supports MCP Apps, such as Claude (web, desktop and mobile), ChatGPT, VS Code, Cursor and Goose Desktop. There is nothing to configure: the server detects these clients when they connect.
The map apps load MapLibre GL JS from https://cdn.jsdelivr.net, so the client must be able to reach cdn.jsdelivr.net as well as api.tomtom.com. A client behind a firewall that blocks jsDelivr renders no maps.
What if my client doesn’t support MCP Apps?
The interactive maps are an enhancement, not a replacement. Every data tool always returns a full text response with all the data (coordinates, addresses, distances, route details, etc.). If your client doesn’t support MCP Apps, you’ll still get the complete text results, but you won’t see the map visualization.
Clients known to render no MCP Apps, such as Claude Code, Gemini CLI, Cline, Zed, Goose CLI, Continue, Amazon Q CLI, opencode and Roo Code, get only the data tools. They don’t see tomtom-dynamic-map, tomtom-data-viz or the show_ui parameter.
Configuration
You can override the automatic detection, for example for a headless agent or a client that renders MCP Apps but isn’t detected.
Remote MCP Server
Add a query parameter to the MCP URL:
https://mcp.tomtom.com/maps?apps=false: data tools only, without mapshttps://mcp.tomtom.com/maps?apps=true: every tool, with maps
Local setup
Set the MCP_APPS environment variable when starting the server:
MCP_APPS=false npx @tomtom-org/tomtom-mcpUse MCP_APPS=true to always get every tool, with maps. MCP_APPS applies to the stdio server; when you run the server in HTTP mode, for example with Docker, use the ?apps= query parameter instead.
Next steps
- Explore all available tools and their parameters
- Try the Example use cases for prompt inspiration
- Learn about Remote vs. local setup for deployment options