TomTom Maps
MCP server by TomTom
Geocode addresses, search places, plan routes, check traffic and render static or dynamic maps with TomTom location services.
Connect to TomTom Maps
TomTom Maps needs an API key. Connect with its own URL and your key:
Send your key in the tomtom-api-key header. mcp.tc never sees or stores keys. Where to get a key
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/tomtomAbout
Connects an assistant to TomTom's location APIs. It covers geocoding, place search, routing, traffic data, and static and dynamic maps, so an assistant can answer location questions and build geospatial workflows with TomTom data.
The hosted endpoint at https://mcp.tomtom.com/maps is in public preview and uses streamable HTTP. It needs a TomTom API key with MCP Server access enabled, sent in the tomtom-api-key header. A local option runs with npx and the TOMTOM_API_KEY environment variable, in stdio or HTTP mode, and requires Node.js 22.
What you can do
- Geocode addresses and place names to coordinates
- Search for places and points of interest
- Calculate routes between locations
- Check traffic conditions
- Generate static maps
- Show dynamic interactive maps
Tools
TomTom Maps lists its tools only to clients with a key, so we can’t show them here.
Example prompts
Geocode Amsterdam Central Station and show it on a map.
Find the route from Rotterdam to Utrecht and tell me about traffic.
Search for coffee shops near Dam Square in Amsterdam.
Create a static map of central Berlin.
Set up
Every client connects to mcp.tomtom.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header "tomtom-api-key: <YOUR_API_KEY>"- Replace the placeholder with your key before you run it, then check it with
/mcpinside Claude Code.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Custom connectors can’t send this server’s key header, so use the
mcp-remotebridge. Open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"tomtom": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.tomtom.com/maps",
"--header",
"tomtom-api-key: <YOUR_API_KEY>"
]
}
}
}- Replace the placeholder with your key and restart Claude Desktop.
The bridge needs Node.js on your computer.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"tomtom": {
"url": "https://mcp.tomtom.com/maps",
"headers": {
"tomtom-api-key": "<YOUR_API_KEY>"
}
}
}
}VS Code
Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:
{
"servers": {
"tomtom": {
"type": "http",
"url": "https://mcp.tomtom.com/maps",
"headers": {
"tomtom-api-key": "${input:tomtom-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "tomtom-api-key",
"description": "tomtom-api-key",
"password": true
}
]
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"tomtom": {
"serverUrl": "https://mcp.tomtom.com/maps",
"headers": {
"tomtom-api-key": "<YOUR_API_KEY>"
}
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add tomtom --url https://mcp.tomtom.com/mapsOr edit ~/.codex/config.toml directly:
[mcp_servers.tomtom]
url = "https://mcp.tomtom.com/maps"
env_http_headers = { "tomtom-api-key" = "TOMTOM_API_KEY" }Codex reads the header values from the environment variables named in env_http_headers.
Gemini CLI
gemini mcp add --transport http --header "tomtom-api-key: <YOUR_API_KEY>" tomtom https://mcp.tomtom.com/mapsThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"tomtom": {
"type": "http",
"url": "https://mcp.tomtom.com/maps",
"headers": {
"tomtom-api-key": "<YOUR_API_KEY>"
}
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.tomtom.com/maps.
FAQ
Can I paste mcp.tc/i/tomtom into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.tomtom.com/maps, so your client talks to TomTom Maps directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.
Does TomTom Maps need an API key or a sign-in?
Yes. TomTom Maps needs an API key, sent as the tomtom-api-key header. Get one from TomTom and keep it in your client’s config, never in a shared file.
Is TomTom Maps a remote or a local server?
Remote. TomTom hosts it at https://mcp.tomtom.com/maps, and it speaks Streamable HTTP. There’s nothing to install.
What can TomTom Maps do?
You can geocode addresses and place names to coordinates, search for places and points of interest and calculate routes between locations.
Which clients can use it?
Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others, and Claude Desktop through the mcp-remote bridge. claude.ai and ChatGPT can’t send a key, so they can’t use it.
Who wrote this page?
mcp.tc’s robot read TomTom Maps’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show TomTom Maps in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/tomtom)<a href="https://mcp.tc/i/tomtom"><img src="https://mcp.tc/i/tomtom/badge.svg" alt="TomTom Maps on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/tomtom.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/tomtom" title="TomTom Maps on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/tomtom.jsonmcp.tc isn’t affiliated with TomTom. This page was built from TomTom Maps’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.