Overview
TomTom Traffic Analytics MCP
Real-time and historical traffic analytics for AI assistants, powered by TomTom MOVE
This is an open-source project. The source code is available on GitHub.
The TomTom Traffic Analytics MCP Server connects AI assistants to the TomTom MOVE traffic analytics platform through the Model Context Protocol (MCP), an open standard that lets AI assistants like Claude use external tools and data sources. This server runs locally on your machine and provides tools for junction monitoring, route tracking, incident detection, and area-wide congestion analysis.
You ask questions in plain language. The AI assistant handles the rest: choosing the right tool, writing SQL queries, and interpreting results. No traffic API expertise required.
Demo
What Makes This Different
Traffic APIs return deeply nested JSON responses that can contain thousands of rows of time-series data, spatial grids, or per-segment metrics. Passing these payloads directly to an LLM consumes the context window and leads to inaccurate statistics when the model attempts to summarize raw numbers.
The Traffic Analytics MCP Server addresses this with server-side SQL filtering. Every tool includes a built-in DuckDB engine that:
- Fetches data from TomTom APIs
- Flattens nested JSON into relational tables
- Executes your SQL queries against those tables
- Returns only the filtered, aggregated results
The AI assistant writes the SQL. The server runs it. Only the query results reach the model, not the raw data.
Learn more in the SQL Filtering guide.
What You Can Build
Traffic Operations
- Monitor junction congestion in real time: delays, queue lengths, stop counts
- Detect and compare traffic incidents across multiple areas simultaneously
- Track travel times and delays on strategic route corridors
Urban Planning & Mobility
- Analyze area-wide congestion trends over weeks with hourly granularity
- Identify congestion hotspots using spatial grid data
Fleet & Logistics
- Monitor route performance with segment-level speed and confidence data
- Identify bottleneck segments where current speed drops below typical
- Compare delay percentages across your entire route portfolio
Comparative Analysis
- Query up to 20 junctions or routes side-by-side in a single request
- Compare incidents across up to 10 named bounding boxes
- Rank, filter, and aggregate across entities using standard SQL
See these in action with full prompts and AI responses in the Example Use Cases.
API Access and Data Setup
The server mixes two TomTom APIs with different setup flows. Knowing which tools work out-of-the-box with a public developer key and which require MOVE Portal data to be configured first is the fastest path to a working integration.
| Tool domain | API key | Data setup needed |
|---|---|---|
| Live Traffic (flow, incidents) | TomTom Developer Portal | None. Works immediately on any coordinates or bounding box. |
| Area Analytics | MOVE Portal | None. Supply any GeoJSON polygon at query time. |
| Junction Analytics | MOVE Portal | Junctions must be created in MOVE Portal first. The MCP queries junctions by their MOVE-assigned IDs, so tomtom-junction-search returns an empty list until you configure monitored junctions in the portal. |
| Route Monitoring | MOVE Portal | Routes must be created in MOVE Portal first. Same pattern as junctions: configure the routes you want to track in the portal before querying. |
If you're new to MOVE Portal, sign up for the 30-day free trial and create your monitored junctions and routes in the portal UI before running the Junction Analytics or Route Monitoring tools.
Works With TomTom MCP Server
This server focuses on traffic analytics: congestion, delays, incidents, and historical trends. For geocoding, routing, search, and map rendering, use the companion TomTom MCP Server. The two servers complement each other and can run side-by-side in any MCP client.
Next Steps
- Quick Setup: Install and configure the server in minutes
- SQL Filtering: Understand the SQL-driven approach
- Available Tools: Browse all 8 tools with parameter and table references
- Use Cases: See example workflows with real prompts and responses