TomTomCAUTION
A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://www.npmjs.com/package/@tomtom-org/tomtom-mcp) [](https://opensource.org/licenses/Apache-2.0)
The TomTom Maps MCP Server simplifies geospatial development by providing seamless access to TomTom’s location services, including search, routing, traffic and interactive maps. It enables easy integration of precise and accurate geolocation data into AI workflows and development environments.
Demo
Table of Contents
- Demo
- Security Notice
- Remote MCP Server (No Installation Required)
- Quick Start
- Prerequisites
- Installation
- Configuration
- Usage
- Integration Guides
- Available Tools
- How dynamic map tool works
- Getting geometry out of a tool response
- Debug UI
- Local Development
- Setup
- Testing
- Testing Requirements
- Project Structure
- Troubleshooting
- API Key Issues
- Test Failures
- Build Issues
- Contributing \& Feedback
- Security
- License
Remote MCP Server (No Installation Required)
Public Preview — The TomTom Maps Remote MCP Server is currently in public preview.
The easiest way to get started is to connect directly to TomTom's hosted MCP Server — no Node.js, Docker, or local setup needed.
Endpoint:
https://mcp.tomtom.com/maps
Prerequisites:
- A valid TomTo
5871729d4e11OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add tomtom-mcp-app-host --env AUTHORIZATION_SERVER_URL=${AUTHORIZATION_SERVER_URL} --env TOMTOM_API_KEY=${TOMTOM_API_KEY} --env ULS_TOKEN_ENDPOINT=${ULS_TOKEN_ENDPOINT} -- npx -y [email protected]{
"mcpServers": {
"tomtom-mcp-app-host": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"AUTHORIZATION_SERVER_URL": "${AUTHORIZATION_SERVER_URL}",
"TOMTOM_API_KEY": "${TOMTOM_API_KEY}",
"ULS_TOKEN_ENDPOINT": "${ULS_TOKEN_ENDPOINT}"
}
}
}
}Exposed tools (14)
14 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
tomtom-area-search | read | area-search: renders boundary polygon and pins, shows POI popup on click |
tomtom-data-viz | read | data-viz: renders data visualization with title overlay |
tomtom-dynamic-map | read | dynamic-map: renders marker at Amsterdam, shows popup on click |
tomtom-ev-search | read | ev-search: renders EV station markers, shows POI popup on click |
tomtom-fuzzy-search | read | fuzzy-search: renders search results, shows POI popup on marker click |
tomtom-geocode | read | geocode: renders map with pins, shows POI popup on marker click |
tomtom-nearby | read | nearby: renders nearby places, shows POI popup on marker click |
tomtom-poi-categories | read | Look up POI category codes from natural language. The poiCategories parameter of the search tools accepts only codes returned by this tool. |
tomtom-poi-search | read | poi-search: renders POI markers, shows popup on click |
tomtom-reachable-range | read | reachable-range: renders the requested range with budget controls |
tomtom-reverse-geocode | read | reverse-geocode: renders location pin, shows POI popup on click |
tomtom-routing | read | routing: renders route on map with waypoint markers |
tomtom-search-along-route | read | search-along-route: renders route with POI markers, shows popup on click |
tomtom-traffic | read | traffic: renders live traffic flow with auto-opened incident popup |
Trust audit
CAUTIONgrade B · trust 85/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (9 observation(s))
- Network
- declared (5 observation(s))
- Shell
- declared (5 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (24)
.claude/skills/coding-guidelines
.claude/skills/mcp-builder
"http://127.0.0.1:6274/oauth/callback",
.mcpbignore
import { createMapControls } from "../../shared/map-controls";import { shouldShowUI, showMapUI, hideMapUI, showErrorUI } from "../../shared/ui-visibility";import { extractFullData } from "../../shared/decompress";import { ensureTomTomConfigured } from "../../shared/sdk-config";import { injectPoiPopupStyles } from "../../shared/poi-popup";["link-local / cloud metadata", "169.254.169.254"],
data_url: "https://169.254.169.254/latest/meta-data/",
appUrl = `http://127.0.0.1:${(server.address() as AddressInfo).port}/app.html`;"http://127.0.0.1:6274/oauth/callback",
"http://127.0.0.1:6274/oauth/callback/debug",
"http://127.0.0.1:8976/cb",
const html = "blob" in content ? atob(content.blob as string) : (content as any).text;
anthropic, mcp
@modelcontextprotocol/ext-apps, @modelcontextprotocol/sdk, @turf/buffer, @types/geojson, axios, compression, cors, dotenv
@modelcontextprotocol/ext-apps, @modelcontextprotocol/sdk, dotenv, react, react-dom, @types/express, @types/node, @types/react
| 23 | Med | CWE-201 | `src/utils/http.ts`, `fetch()` | By design | The single `fetch` the three auth calls now share (PR #306). Supersedes #4 and the equivalent `tokenExchanger` / `mcpProjectResolver
images/claude_demo.gif
4. Select all available APIs to ensure full access, assign a name to your key, and click **Create**.
- A valid TomTom API key with MCP Server access enabled (see [API Key Management](https://developer.tomtom.com/platform/documentation/dashboard/api-key-management))
cat .env # Check API key
Gates applied: no_behavioural_pass.
5871729d4e11full audit observations/trust-audit/mcp-server/tomtom-international__tomtom.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 5871729d4e11 | CAUTION | B | 85 | first audit |
Questions
What is the TomTom MCP server?
A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.
What tools does TomTom expose?
14 in total: 14 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is TomTom safe to connect to an agent?
With care. The audit graded it B (85/100) and found 24 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does TomTom need?
It reads AUTHORIZATION_SERVER_URL, TOMTOM_API_KEY and ULS_TOKEN_ENDPOINT from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does TomTom run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as tomtom-mcp-app-host at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (5871729d4e11), read on 2026-10-08. The repository is watched and re-audited when it changes.