Quick setup
Quick setup
Get started with TomTom’s location services in your AI workflows using our Remote MCP Server. No installation required!
Prerequisites
Before you begin, ensure you have:
- A valid TomTom API key: sign up for a free account to get your API key
- Ensure that your key has access to the MCP product and different APIs available through the MCP.
- Inspect your API key’s configuration at API & SDK Keys
- Tick “All” under “Edit key”, or enable “MCP Server”, “Map Display API”, “Routing API”, “Search API”, “Geocoding API”, “Reverse Geocoding API” and “Traffic API”.
- An MCP-compatible AI client (VS Code with GitHub Copilot, OpenAI Agents, Claude Desktop, etc.). See Integration guides for client-specific setup
Step 1: Get your endpoint
The TomTom Maps Remote MCP Server is available at:
https://mcp.tomtom.com/mapsNo installation is required: the server is ready to use with your API key.
Step 2: Configure your MCP client
Configure your AI client to connect to the TomTom Maps Remote MCP Server using your API key in the request headers.
{ "mcpServers": { "tomtom-maps-mcp": { "type": "http", "url": "https://mcp.tomtom.com/maps", "headers": { "tomtom-api-key": "your_api_key_here" } } }}Replace "your_api_key_here" with your actual TomTom API key from my.tomtom.com.
Clients without MCP Apps
The server detects clients that cannot render interactive maps, such as Claude Code, Gemini CLI, Cline and Zed, and gives them only the data tools. To choose for yourself, for example for a headless agent, add a query parameter to the URL:
https://mcp.tomtom.com/maps?apps=false: data tools only, without mapshttps://mcp.tomtom.com/maps?apps=true: every tool, with maps
For specific client integration instructions, see our Integration guides.
Step 3: Test the connection
Once configured, test that your AI assistant can access TomTom’s services by asking a simple location-based question:
What's at the coordinates 52.3676, 4.9041?Your AI assistant should be able to use the TomTom Maps MCP Server to retrieve the address and other location details from the TomTom APIs.
Authentication & charging
All requests to the TomTom Maps MCP Server use your API key for authentication. API usage is tracked and charged according to TomTom’s standard pricing.
Learn more: For detailed pricing information, visit https://docs.tomtom.com/pricing
Next steps
- Explore Available tools to see what you can do with TomTom Maps MCP
- Check out Integration guides for specific client configurations
- Review Use cases for inspiration on what to build