Geodb Cities MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host configuration (not applicable for stdio transport but listed in documentation). | |
| PORT | No | Port configuration (not applicable for stdio transport but listed in documentation). | |
| API_KEY | Yes | Your API key for the Geodb Cities API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| place_distanceC | Gets this place's distance to the given place. |
| place_timeB | Get this place's current time in ISO-8601 format: HHmmss.SSSZ |
| place_date_timeB | Get this place's current date-time in ISO-6801 format: yyyyMMdd'T'HHmmssZ |
| place_located_inA | Get the details for the containing populated place (e.g., its county or other administrative division), including location coordinates, population, and elevation above sea-level (if available). Currently, this data is highly dependent on whether the Wikidata locatedIn relation is properly defined. If you see an issue, please propose a change to the corresponding Wikidata entry. |
| place_detailsB | Get the details for a specific place, including location coordinates, population, and elevation above sea-level (if available). |
| city_located_inB | Get the details for the containing populated place (e.g., its county or other administrative division), including location coordinates, population, and elevation above sea-level (if available). Currently, this data is highly dependent on whether the Wikidata locatedIn relation is properly defined. If you see an issue, please propose a change to the corresponding Wikidata entry. |
| places_near_locationC | Get places near the given location, filtering by optional criteria. |
| places_near_placeC | Get places near the given place, filtering by optional criteria. |
| country_placesB | Get the places in the given country. |
| country_region_divisionsC | Get the administrative divisions in the given region. |
| admin_division_detailsB | Get the details for a specific administrative division, including location coordinates, population, and elevation above sea-level (if available). |
| cities_near_divisionC | Get cities near the given administrative division, filtering by optional criteria. |
| admin_divisionsB | Find administrative divisions, filtering by optional criteria. If no criteria are set, you will get back all known divisions with a population of at least 1000 |
| country_region_placesC | Get the places in the given region. |
| placesC | Find places, filtering by optional criteria. If no criteria are set, you will get back all known places. |
| time_zoneC | Get the time-zone current time in ISO-6801 format: HHmmss.SSSZ |
| admin_divisions_near_locationC | Get administrative divisions near the given location, filtering by optional criteria. |
| admin_divisions_near_divisionC | Get divisions near the given administrative division, filtering by optional criteria. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.