TomTom Maps MCP Server

Remote vs. local setup

Remote vs. local setup

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

Comparison table

FeatureRemote MCP ServerLocal setup
Installation requiredNoYes
MaintenanceManaged by TomTomSelf-managed
Automatic updatesYesManual
CustomizationLimitedFull
Map dataTomTom Orbis MapsTomTom Orbis Maps
API usage chargesYesYes
Best forMost usersDevelopers and custom deployments

The Remote MCP Server is a fully managed service hosted by TomTom: no installation, no maintenance, always up to date.

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

Get started: Follow the Quick setup guide.

Local setup

Run the TomTom Maps MCP Server on your own infrastructure via npx or Docker. Available as open source on GitHub.

When to use:

  • Your MCP client does not support remote HTTP with custom headers
  • You have specific deployment or security requirements
  • You want to customize or contribute to the server code

Claude Desktop users: A pre-built extension is available that requires no local setup. See the Claude Desktop integration guide for details.

The local setup requires Node.js 22 or later (not needed for Docker). Keeping a local deployment up to date is your responsibility. To stay on a specific version, pin it, for example npx @tomtom-org/tomtom-mcp@1.6.12. The Remote MCP Server always runs the latest release.

Get started: See the GitHub repository README for installation instructions.