Claude Desktop
Claude Desktop Integration Guide
This guide explains how to configure Claude Desktop to use the TomTom Traffic Analytics MCP Server for traffic analysis queries.
Prerequisites
- Claude Desktop installed
- Node.js 22.9.0 or higher and TomTom API keys. See Quick Setup for details
Setup
-
Open Claude Desktop and navigate to Settings → Developer → Edit Config.
-
Add the following to your
claude_desktop_config.json:1{2 "mcpServers": {3 "tomtom-traffic-analytics": {4 "command": "npx",5 "args": ["-y", "@tomtom-org/tomtom-traffic-analytics-mcp@latest"],6 "env": {7 "TOMTOM_MOVE_PORTAL_KEY": "your_move_portal_key",8 "TOMTOM_API_KEY": "your_tomtom_developer_key"9 }10 }11 }12}Replace the API key values with your actual keys. Omit
TOMTOM_API_KEYif you only need junction, route, and area analytics tools. -
Save the file and restart Claude Desktop.
-
Open a new conversation. You should see the Traffic Analytics tools available in the tools menu (hammer icon).
Test the Integration
Ask Claude a traffic analytics question to verify the connection:
Show me all active junctions grouped by country
Claude should use the tomtom-junction-search tool with a SQL query and return a structured summary.
What to Try Next
Once the connection is working, try these prompts to explore what's possible:
Which of my junctions have the worst delays right now? Show me the top 5.
Are any of my monitored routes significantly delayed? Show me the bottleneck segments.
Compare traffic incidents between downtown Amsterdam and the A10 ring road.
For more workflows with full prompts and expected responses, see the Example Use Cases.
Troubleshooting
| Problem | Possible Fix |
|---|---|
| Tools not appearing | Restart Claude Desktop after saving the config file |
| Connection timeout | Check your internet connection and API key validity at move.tomtom.com |
For other common issues, see Quick Setup > Common Issues.
Next Steps
- Example Use Cases: Full workflows with prompts and AI responses
- Which API key do I need?: Breakdown of which key each tool requires
- Running alongside TomTom MCP Server: Use both servers side-by-side
- SQL Filtering: How the SQL-driven approach works under the hood