# Tomtom [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/pipeworx-io/mcp-tomtom  
**GitHub Stars:** 0  
**npm Downloads (last month):** 432  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tomtom

## Description
TomTom MCP — wraps the TomTom Search & Routing APIs (api.tomtom.com)

## Tools
Capabilities this server exposes over MCP:

- **geocode** — Geocoding: convert an address, place name, or free-text location query into geographic coordinates (latitude/longitude). Returns formatted address, country, lat, lon, type, and match score. Example: geocode({ query: "350 5th Ave, New York" })
- **search_poi** — Search for points of interest (POIs) — businesses, landmarks, restaurants, gas stations, etc. — by name or category, optionally near a lat/lon center within a radius. Returns name, category, address, coordinates, phone, url, and distance. Example: search_poi({ query: "coffee", lat: 40.748, lon: -73.985, radius: 1000 })
- **reverse_geocode** — Reverse geocoding: convert latitude/longitude coordinates into a human-readable street address. Returns the freeform address, country, municipality, street name, postal code, and position. Example: reverse_geocode({ lat: 40.748, lon: -73.985 })
- **route** — Traffic-aware routing / directions: calculate the best route between two points and return distance plus travel time computed with live traffic. Reports traffic delay so you get realistic ETAs, not free-flow estimates. Supports car, truck, pedestrian, and bicycle travel modes. Example: route({ from_lat: 40.748, from_lon: -73.985, to_lat: 40.689, to_lon: -74.044 })

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "tomtom": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-tomtom"]
  }
}
```

## Documentation

## What Tomtom MCP server does

Tomtom MCP server gives MCP-compatible AI clients access to TomTom’s Search and Routing APIs. The package covers four location operations:

- `geocode` converts an address, place name, or free-text location into latitude and longitude. Results can include a formatted address, country, location type, and match score.
- `search_poi` finds points of interest such as businesses, landmarks, restaurants, and fuel stations. Searches can use a name or category and can be constrained by a coordinate center and radius.
- `reverse_geocode` turns coordinates into a readable address, including fields such as municipality, street, postal code, country, and position.
- `route` calculates directions between two coordinates. It returns distance, travel time based on live traffic, and traffic delay, with car, truck, pedestrian, and bicycle modes supported.

These tools suit agents that need structured geographic results rather than only text-based map answers.

## How it works

The hosted MCP endpoint is `https://gateway.pipeworx.io/tomtom/mcp`. A client connects to that URL and discovers the TomTom tools through the normal MCP initialization and tool-listing flow. The endpoint also exposes shared Pipeworx meta-tools, so its tool list is larger than the four TomTom-specific tools. The exact scope is reported by the connection’s `initialize` response.

The same gateway also provides a full endpoint at `https://gateway.pipeworx.io/mcp`. Either gateway URL can use `ask_pipeworx` to route a plain-language request across the broader Pipeworx catalog. That routing capability is separate from the four tools included in the local package.

For clients or applications that do not use MCP, the gateway offers HTTP tool calls. For example, a caller can send a JSON POST request to `/v1/tools/tomtom_geocode` with a `query` value.

## Setup and configuration

Add the hosted endpoint to an MCP client as a server URL:

```json
{
  "mcpServers": {
    "tomtom": {
      "url": "https://gateway.pipeworx.io/tomtom/mcp"
    }
  }
}
```

The package also supports local stdio execution without a Pipeworx account or gateway round trip:

```json
{
  "mcpServers": {
    "tomtom": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-tomtom"]
    }
  }
}
```

Running `npx -y @pipeworx/mcp-tomtom` directly starts the local process. In this mode, the server communicates over stdin and stdout and lists only the TomTom pack’s tools.

## Tools and capabilities

Use `geocode` for forward address lookup, `reverse_geocode` for address lookup from coordinates, and `search_poi` for nearby or category-based place discovery. Use `route` when travel mode and traffic-aware timing matter. Route inputs use origin and destination latitude/longitude values; POI searches may also include a radius around a coordinate center.

## Limitations and notes

The hosted pack endpoint always includes shared Pipeworx meta-tools; there is no documented option to mount the pack without them. Those additional schemas may increase context usage. The local stdio package avoids those shared tools but does not provide gateway-wide routing.

_Full upstream README: https://allmcps.com/mcp/tomtom/readme_