M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
T

TomTom Maps MCP Server

Official
TomTom location, search, routing, and traffic data for AI workflows.
How to install ↓ Compare GitHub source repository ↗
Category
Other #51 of 230
Stars
★ 56 Popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js 22.x · Docker · Hosted (no local runtime)
Credentials
API key / credential required
License
Apache-2.0
Last commit
Tools
16
63FMRS · C

An official TomTom-maintained MCP server covering geocoding, search, routing, traffic, and map rendering, with remote HTTP, local stdio, local HTTP, and Docker usage options. A TomTom API key is required, while Orbis and EV capabilities have preview and access limitations.

Strongest · Documentation 15/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
12/20
Maintenance
12/20
Documentation
15/20
Setup experience
14/20
Why each score
Reliability 10/20
The README describes stdio, HTTP, Docker, and multiple tools, and states that unit, stdio, and HTTP tests exist. However, no source files, manifest, or CI configuration were provided, so MCP initialization, tool-list consistency, error handling, and actual execution paths cannot be statically verified. Tests require a real API key, reducing controllability; therefore the score is kept below 12.
Security and permissions 12/20
Credentials can be supplied through an environment variable, .env, or an HTTP header, and the documented tools primarily perform geospatial search, routing, traffic, and map queries without shown delete, payment, deployment, or remote-command side effects. Points are deducted because the documentation recommends selecting all available APIs rather than demonstrating least privilege, and does not sufficiently establish external-network disclosure, location-data boundaries, credential protection in logs, rate limits, cost controls, or request confirmation. No stated security red line is evidenced.
Maintenance 12/20
The project states an Apache-2.0 license, identifies TomTom Navigation B.V., and provides contribution, DCO, code-of-conduct, and vulnerability-reporting channels; the repository is not archived. Points are deducted because no commit cadence, release history, dependency-update evidence, CI status, or security-response timing is supplied. A 2025 copyright notice and non-archived status do not establish sustained maintenance.
Documentation 15/20
The README covers remote and local installation, Node.js and pnpm prerequisites, authentication, stdio/HTTP/Docker usage, client configuration, tool inventory, backend differences, debug UI, testing, and some troubleshooting. Points are deducted because reviewable parameter schemas, input limits, API quotas, cost, privacy, and retention information are absent; the manifest is unavailable, and tests consume real quota, so completeness cannot be independently verified from the supplied material.
Setup experience 14/20
The project provides remote HTTP, npm/npx, Docker, Docker Compose, and configuration examples for Claude Desktop, VS Code, Cursor, Windsurf, and Smolagents, making the main paths relatively clear. Points are deducted because a TomTom API key is required, the remote service is in public preview, some clients must support HTTP with custom headers, and local use requires Node.js 22 or pnpm. No source files or CI evidence were supplied to verify reproducible installation.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • AI agents needing global geocoding, place search, routing, and traffic data
  • Developers integrating TomTom mapping capabilities with Claude Desktop, VS Code, Cursor, or Windsurf
  • Applications that need HTTP or Docker-based map-service integration

Not for

  • Applications that do not need TomTom location or navigation data
  • Users who cannot provide a TomTom API key
  • Offline mapping or offline API-data scenarios

Required permissions

  • Requires a valid TomTom API key.
  • The key must have MCP Server access enabled; local tests call real APIs and consume API quota.
  • TomTom Orbis Maps and some EV features may require additional account access.

Risks and side effects

  • The MCP client or operator is responsible for updates, patches, and security configuration of local deployments.
  • API calls consume quota.
  • TomTom Orbis Maps and some EV features are in public preview and may produce 403 errors or be unavailable to some accounts.
  • Map and traffic results depend on TomTom services and the selected backend.

Setup

Before you start

Runtime：Node.js 22.x · Docker · Hosted (no local runtime)

TOMTOM_API_KEY requiredsecret API key created on the TomTom Developer Portal (my.tomtom.com); required.
Other optional settings (3)
MAPS optional Selects the map backend: tomtom-maps (default) or tomtom-orbis-maps (public preview).
PORT optional Port for the HTTP server, defaults to 3000.
LOG_LEVEL optional Logging level: debug, info, warn, or error; defaults to info.

The remote preview server requires no local installation: replace TOMTOM_API_KEY with a valid key and add the configuration to an MCP client that supports custom HTTP headers. Alternatively, use Node.js 22.x to install with npm or run @tomtom-org/tomtom-mcp@latest with npx. For local HTTP or Docker deployments, provide the key in the tomtom-api-key request header.

claude_desktop_config.json 
{"mcpServers":{"tomtom-mcp":{"type":"http","url":"https://mcp.tomtom.com/maps","headers":{"tomtom-api-key":"your_api_key_here"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "tomtom-mcp": {
      "type": "http",
      "url": "https://mcp.tomtom.com/maps",
      "headers": {
        "tomtom-api-key": "your_api_key_here"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http tomtom-mcp https://mcp.tomtom.com/maps --header 'tomtom-api-key: your_api_key_here'

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Check that tools like tomtom-geocode appear in the client's tool list, then run a geocode query for 'Amsterdam Central Station' — returned coordinates confirm the connection works.

Troubleshooting

  1. Verify that TOMTOM_API_KEY is set and has the required API permissions.
  2. For 403 errors, select all available products for the key in the TomTom Developer Portal; if the issue remains, use the tomtom-maps backend.
  3. HTTP mode requires the key in the tomtom-api-key header.
  4. In dual-backend mode, use tomtom-maps-backend to select the backend; if MAPS is set at startup, that header is ignored.
  5. Before local testing, confirm that .env exists and remember that tests make real API requests.

Things to try

Once connected, you can ask your AI assistant things like:

  • Geocode the address 'Amsterdam Central Station' to coordinates.
  • Find restaurants within 1 km of my current location.
  • Calculate the optimal route from Amsterdam to Brussels and show real-time traffic incidents along it.
  • Generate a static map image of Amsterdam with custom markers.

Tools 16

tomtom-geocode read-only
Converts addresses into coordinates.
tomtom-reverse-geocode read-only
Converts GPS coordinates into addresses.
tomtom-fuzzy-search read-only
Provides intelligent search with typo tolerance.
tomtom-poi-search read-only
Finds points of interest and businesses by category.
tomtom-nearby read-only
Discovers services or places within a radius.
tomtom-routing read-only
Calculates optimal routes between locations.
tomtom-waypoint-routing read-only
Plans routes with multiple stops.
tomtom-reachable-range read-only
Calculates reachable areas using a time or distance budget.
Show 8 more tools
tomtom-traffic read-only
Provides real-time traffic incident data.
tomtom-static-map read-only
Generates custom map images.
tomtom-dynamic-map read-only
Renders maps with custom markers, routes, and traffic visualization.
tomtom-ev-routing read-only
Plans long-distance EV routes with automatic charging-stop optimization.
tomtom-search-along-route read-only
Finds points of interest such as restaurants, gas stations, and hotels along a route.
tomtom-area-search read-only
Searches for places within a circle, polygon, or bounding-box area.
tomtom-ev-search read-only
Finds EV charging stations with real-time availability and connector types.
tomtom-data-viz read-only
Visualizes custom GeoJSON data on a TomTom basemap using markers, heatmaps, clusters, and choropleths.

Use cases

Address and coordinate conversion
Place, POI, and nearby-service search
Point-to-point and multi-stop routing
Traffic incident lookup
Static and dynamic map image generation
EV routing and charging-station search with the Orbis backend

Supported clients

Claude Desktop
GitHub Copilot
Cursor
Windsurf
SmolagentsPartial support

Listed from the project's documentation, not tested by this site.

Overview

TomTom Maps MCP Server is maintained by TomTom and provides AI agents and development environments with location services, geocoding, search, routing, traffic data, and static map capabilities. It supports the standard TomTom Maps backend and the optional TomTom Orbis Maps backend.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 654 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 7e3a2e203d40 Data synced 2026-10-12 Read the FMRS scoring method