TomTom Traffic Analytics MCP

Useful for

Use cases llm-inferred

Traffic baseline for a junction or access assessment using junction archive data · Route delay and congestion review for a corridor or road-scheme appraisal · Area traffic context for a Transport Assessment or construction traffic management review · Live traffic flow and incident checks at a road segment during site investigation

Audience llm-inferred

civils engineers · highways engineers · transport planners · GIS analysts

Limitations

Constraints llm-inferred

Two separate API keys and accounts are needed: MOVE Portal for analytics tools, TomTom Developer for live traffic tools · MOVE Portal access is documented as a 30-day free trial; longer-term pricing is not stated · All analytical tools require a sql_queries parameter (DuckDB filtering), so users must write SQL against the tool's tables · Node.js 22.12+ is required to run the server · Data coverage, resolution and update frequency are not stated in the docs · Integration tests need valid keys and API quota, so the server depends on external TomTom service availability

Example tool calls docs-verified

{
  "tool": "tomtom-junction-archive",
  "arguments": {
    "junctionIds": [
      "abc-123"
    ],
    "sql_queries": {
      "top_delays": "SELECT approach_id, delay_sec FROM approaches ORDER BY delay_sec DESC LIMIT 5"
    }
  }
}