Remote vs. Local Setup

Remote vs. Local Setup

The TomTom MCP Server is available in two deployment modes: a Remote MCP Server (recommended for most users) and a Local Setup (for advanced use cases).

Remote MCP Server (Recommended)

The Remote MCP Server is a fully managed service hosted by TomTom. It's the easiest way to integrate TomTom's location services into your AI workflows.

Benefits

• Zero Installation: No need to install Node.js, Docker, or manage dependencies
• Always Up-to-Date: Automatic updates with the latest features and bug fixes
• Scalable: TomTom manages the infrastructure and scaling
• Simple Configuration: Just add the endpoint URL and your API key in the header tomtom-api-key.

Endpoint

https://mcp.tomtom.com/maps

Map Backend

• Uses TomTom Maps backend only (no TomTom Orbis Maps support)
• All standard TomTom location services are available
• For TomTom Orbis Maps backend access, use the local setup option

When to Use

• You want the simplest setup experience
• You don't need to modify the MCP server code
• You prefer a managed service without maintenance overhead such as security updates
• TomTom Maps backend meets your requirements

Local Setup

The local setup allows you to run the TomTom MCP Server on your own infrastructure. This option is available as open source on GitHub.

Benefits

• Full Control: Customize and extend the server code
• Source Code Access: Review, modify, and contribute to the codebase
• Backend Choice: Access to both TomTom Maps and TomTom Orbis Maps (Public Preview) backends
• Flexible Deployment: Run in your own environment or infrastructure

Map Backend Options

• TomTom Maps (default): Standard TomTom map backend
• TomTom Orbis Maps (Public Preview): TomTom's next-generation mapping platform - set MAPS=orbis to use

When to Use

• You need to integrate with Claude Desktop, or other client that does not support remote mcp with custom headers
• You have specific deployment or security requirements
• You want to contribute to the open source project
• You need to run the server in your own environment
• You require access to the TomTom Orbis Maps backend (Public Preview)

Setup Instructions

For local installation instructions, see the GitHub repository README.

Authentication & API Keys

Both remote and local deployments use API keys for authentication and billing:

Getting Your API Key

1. Create a free account at developer.tomtom.com
2. Navigate to your dashboard to generate an API key, ticking "All" to add the necessary products.
3. Use this key in the next steps to authenticate your requests

Configuration

• Remote Server: Include your API key in the client configuration under the header tomtom-api-key
• Local Server: Pass your API key as an environment variable (STDIO) or a header (HTTP), see the GitHub repository

Usage & Charging

All API calls through the TomTom MCP Server (both remote and local) count towards your API usage and are charged according to TomTom's standard API pricing.

How It Works

• Every tool call made through the MCP server invokes TomTom APIs
• Usage is tracked against your API key
• Billing is based on the number and type of API calls made

Pricing

For detailed pricing information, visit: https://developer.tomtom.com/pricing

Free Tier

TomTom offers a free tier for developers to get started. Check the pricing page for current limits and rates.

Comparison Table

Getting Started

• For most users: Follow the Quick Setup guide to connect to the Remote MCP Server
• For local deployment: Visit the GitHub repository for installation instructions