Geonames vs Tomtom
A side-by-side look at the Geonames 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 Geonames 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.
Which MCP server should you choose?
Choose Geonames when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_geonames, get_nearby, get_timezone.
Choose Tomtom when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
geocode, search_poi, reverse_geocode.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 52/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 | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Geonames | View Tomtom |
Tools & capabilities
Geonames tools 4
search_geonamesSearch for places (cities, towns, landmarks, regions) by name and get which STATE / PROVINCE / COUNTY / PREFECTURE / administrative division (German Bundesland, UK county, Canadian province, Japanese prefecture, Indian/Australian/Mexican state, etc.) they are in, plus country, coordinates, populati…get_nearbyFind places near a given latitude/longitude. Returns nearby cities, landmarks, and features sorted by distance. Example: get_nearby(48.8566, 2.3522) for places near Paris.get_timezoneGet timezone information for a latitude/longitude location. Returns timezone ID, GMT offset, DST offset, current local time, sunrise, and sunset. Example: get_timezone(40.7128, -74.0060) for New York.find_postal_codesLook up postal/ZIP codes and places by each other. Pass "postal_code" (+ country) to find the place(s) a code maps to ("what city is ZIP 90210"); or pass "place" (+ country) to find the postal codes for a place name ("postal codes for Paris"). Returns place name, country, admin region (state/county…
Tomtom tools 4
geocodeGeocoding: 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 })
Ready-to-paste client configs
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.
Geonames
{
"mcpServers": {
"geonames": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-geonames"
]
}
}
}
Tomtom
{
"mcpServers": {
"tomtom": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tomtom"
]
}
}
}
Frequently asked questions
Geonames is categorized under Location Services and uses a local stdio subprocess. Tomtom belongs to Location Services and uses a local stdio subprocess. Pick Geonames for location services work and Tomtom for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Geonames has no declared pricing — check the project's own site. Tomtom has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add geonames and tomtom as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Geonames has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Tomtom has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
