Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official

tomtom-traffic

Retrieve real-time and future traffic incidents by specifying area, language, and filters. Optimize routes and monitor conditions with precise bounding box, category, and time-based filtering for improved traffic management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxNoBounding box for traffic area: 'minLon,minLat,maxLon,maxLat'. Example: '-74.02,40.70,-73.96,40.80' for lower Manhattan. Use smaller areas for better results.
categoryFilterNoFilter by incident categories (comma-separated): '0' (Accident), '1' (Fog), '2' (Dangerous Conditions), '3' (Rain), '4' (Ice), '5' (Lane Restrictions), '6' (Lane Closure), '7' (Road Closure), '8' (Road Works), '9' (Wind), '10' (Flooding), '11' (Detour), '14' (Cluster).
incidentTypesNoFilter by incident types (comma-separated): '0' (Accident), '1' (Fog), '4' (Ice), '5' (Lane Restrictions), '7' (Closure), '8' (Roadworks).
languageNoLanguage for incident descriptions: 'en-US', 'de-DE', 'fr-FR', 'es-ES'. Default: 'en-US'.
maxResultsNoMaximum incidents to return (1-1000). Use 10-20 for readability in high-traffic areas.
tNoUnix Timestamp in seconds for traffic model. Use current time if not provided.
timeFilterNoTime validity filter: 'present' (current), 'future' (upcoming), 'all' (both). Default: 'present'.
Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tomtom-international/tomtom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server