A side-by-side look at the OpenStreetMap and Tomtom MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenStreetMap for location services work as a local process; choose Tomtom for location services as a local process. You can also run both side by side in one mcpServers block.
geocode, reverse_geocode, route.geocode, search_poi, reverse_geocode.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 11 | 4 |
| Full listing | View OpenStreetMap | View Tomtom |
geocodePlace name/address → coordinates (Nominatim or Photon)reverse_geocodeCoordinates → nearest addressrouteDistance and duration between 2+ waypoints, `foot`/`car`/`bike`; optional turn-by-turn summaryroute_matrixTravel time/distance from every origin to every destination in one calloptimize_routeBest visiting order for a set of stops (traveling-salesman, OSRM trip)isochroneReachable area within a time or distance budget (Valhalla, or ORS with key)find_nearby_poisPOIs around a location by category or raw OSM tag, sorted by distance (Overpass)poi_detailsFull OSM record of one element: opening hours, website, phone, …suggest_meeting_pointFair meeting venue for 2–8 people (balanced travel times)straight_line_distanceGreat-circle distance, computed offlinemap_linkopenstreetmap.org marker / directions links, computed offlinegeocodeGeocoding: 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_poiSearch 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_geocodeReverse 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 })routeTraffic-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 })Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"openstreetmap": {
"command": "npx",
"args": [
"-y",
"osm-mcp"
]
}
}
}
{
"mcpServers": {
"tomtom": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tomtom"
]
}
}
}