← Directory
mcp · Global
TomTom Maps MCP Server
Official TomTom location services — search, geocoding, routing, traffic
Feature or claim this listing
Feature this listing — founding Featured slots are 50% off for 6 monthsRepresent TomTom Maps MCP Server? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.
What's in it
- Data offered docs-verified
- forward geocoding (address to coordinates) · reverse geocoding (coordinates to address) · fuzzy search · POI search by category · nearby POI search within a radius · POI category list · routing with optional stops · traffic incidents · search along a route corridor · area search (circle, polygon or bounding box) · EV charging station search · dynamic interactive map · GeoJSON data visualisation
- Coverage llm-inferred
- Global
- Formats docs-verified
- MCP stdio · MCP HTTP · JSON · GeoJSON
- Access docs-verified
- TomTom API key required, with MCP Server access enabled on the key; licence Apache-2.0
Useful for
- Use cases llm-inferred
- Geocode client site addresses and reverse-geocode survey coordinates for site visit records · Pull traffic incidents and routed distances along haulage or site access routes for construction logistics · Find receptor POIs (schools, hospitals, care homes) within a radius of a site for stakeholder mapping · Visualise GeoJSON survey or asset points on a basemap for client presentations
- Audience llm-inferred
- GIS analysts · civils and transport planners · site logistics planners · developers integrating location services into AI workflows
Limitations
- Constraints docs-verified
- Remote MCP server is in public preview · Requires a TomTom API key with MCP Server access enabled · Clients that render no MCP apps (e.g. Claude Code, Gemini CLI, Cline, Zed) get only the data tools, without the dynamic map or data-viz tools · Map apps load MapLibre GL JS from cdn.jsdelivr.net, so the client must be able to reach jsDelivr as well as api.tomtom.com · Local deployments need Node.js 22.x, and keeping them updated is the client/operator's responsibility · Coverage area, data vintage and rate limits are not stated in the docs · UK-specific coverage is not documented
Example tool calls docs-verified
Forward geocode a place name or address to coordinates
{
"tool": "tomtom-geocode",
"arguments": {
"query": "Amsterdam Central Station"
}
}- Licence
- Apache-2.0
- Authentication
- API key via env: API_KEY, TOMTOM_API_KEY (auto-extracted from README)
- GitHub stars
- 57
- Last commit
- 16/10/2026
- Last successful page check
- 14/10/2026
- Page health
- healthy
- Package
- npm:@tomtom-org/tomtom-mcp
- Verification
- Not independently verified
Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.
Provenance & evidence
Verified via GitHub API (2026-10-15). Tools/install/auth auto-extracted from README.
Metadata observed 16/10/2026 · research sweep: manual-2026-10-15 (sparkgeo/geo-mcp-servers)