Geodb Cities MCP Server
Related Servers
Alternatives to Geodb Cities MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides access to the City By Api Ninjas API to retrieve detailed city information worldwide. Users can search and filter results by name, country, population range, and geographic coordinates.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables exploration of geographical data including countries, cities, states/provinces, and regions through a SQLite database. Supports searches by name, location coordinates, currency, and regional groupings with comprehensive statistical queries.6-
- AlicenseNot gradedqualityBmaintenanceEnables querying country, state, and city data through the CountryStateCity API, accessible via natural language.282 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides complete world location data (countries, states, cities) as an MCP server for AI assistants, enabling search and retrieval of geographic information through 11 tools and 5 resources.182 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables geographic utilities from public APIs: geocoding addresses and places, reverse geocoding coordinates, retrieving country details, timezone data, and sunrise/sunset times through natural language requests.101 npm1MIT
- AlicenseCqualityDmaintenanceEnables geocoding and reverse geocoding operations to convert city names to coordinates and coordinates to location names using the API Ninjas service.2MIT
TDQS
Scored across 18 tools
There is significant overlap between tools like 'city_located_in' and 'place_located_in' which serve similar purposes for different entity types, and 'place_time' vs 'place_date_time' vs 'time_zone' which all handle time-related queries with subtle distinctions. However, most tools have clear primary functions (e.g., 'admin_divisions_near_location' vs 'places_near_location') that help differentiate them.
The naming follows a consistent snake_case pattern throughout with clear verb_noun or noun_verb_noun structures (e.g., 'admin_divisions_near_location', 'place_details'). Minor inconsistencies exist like 'place_date_time' using an incorrect ISO standard reference (6801 instead of 8601) and 'time_zone' being more terse than others, but overall the pattern is predictable.
With 18 tools, the count is slightly high but reasonable for a geographic database server covering administrative divisions, cities, places, and time data. It provides comprehensive query capabilities without being overwhelmingly large, though some consolidation might improve coherence.
The tool set offers complete coverage for querying geographic entities (places, cities, administrative divisions) with details, proximity searches, containment relationships, and time information. There are no obvious gaps—agents can retrieve, filter, and relate geographic data effectively across the domain.