MCP server integrating TomTom APIs
MCP server integrating TomTom APIs. That is what the tomtom mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The TomTom Maps MCP Server simplifies geospatial development by providing seamless access to TomTom’s location services, including search, routing, traffic and static maps data. It enables easy integration of precise and accurate geolocation data into AI workflows and development environments.
The server publishes 14 tools. What each one is for:
tomtom-geocode — Convert addresses to coordinates with global coveragetomtom-reverse-geocode — Get addresses from GPS coordinatestomtom-fuzzy-search — Intelligent search with typo tolerancetomtom-poi-search — Find specific business categoriestomtom-nearby — Discover services within a radiustomtom-routing — Calculate optimal routes between locationstomtom-waypoint-routing — Multi-stop route planning Routing APItomtom-reachable-range — Determine coverage areas by time/distancetomtom-traffic — Real-time incidents datatomtom-static-map — Generate custom map imagestomtom-dynamic-map — Advanced map rendering with custom markers, routes, and traffic visualizationPrerequisites — For more details, visit the [TomTom API Key Management Documentation](https://developer.tomtom.com/platform/documentation/dashboard/api-key-managementConfiguration is passed through the environment: TOMTOM_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tomtom MCP's toolset — tomtom-geocode, tomtom-reverse-geocode, tomtom-fuzzy-search and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tomtom-international; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Tomtom MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| tomtom-geocode | Convert addresses to coordinates with global coverage |
| tomtom-reverse-geocode | Get addresses from GPS coordinates |
| tomtom-fuzzy-search | Intelligent search with typo tolerance |
| tomtom-poi-search | Find specific business categories |
| tomtom-nearby | Discover services within a radius |
| tomtom-routing | Calculate optimal routes between locations |
| tomtom-waypoint-routing | Multi-stop route planning Routing API |
| tomtom-reachable-range | Determine coverage areas by time/distance |
| tomtom-traffic | Real-time incidents data |
| tomtom-static-map | Generate custom map images |
| tomtom-dynamic-map | Advanced map rendering with custom markers, routes, and traffic visualization |
| Prerequisites | For more details, visit the [TomTom API Key Management Documentation](https://developer.tomtom.com/platform/documentation/dashboard/api-key-management). |
| Installation | The Installation tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
**TomTom Orbis Maps:**
```json
{
"mcpServers": {
"tomtom-mcp": {
"type": "http",
"url": "https://mcp.tomtom.com/maps",
"headers": {
"tomtom-api-key": "your_api_key_here",
"tomtom-maps-backend": "tomtom-orbis-maps"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TOMTOM_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.