MCP-Server für die Geomelon geografische API. Stellt Städte, Länder, Regionen und Sprachen als Tools bereit, die von jedem MCP-kompatiblen KI-Client aufgerufen werden können.
Zwei Transporte sind enthalten:
Binärdatei | Transport | Anwendungsfall |
| stdio | Lokale Clients — Claude Desktop, Cursor, Cline, Continue |
| HTTP (Streamable) | Remote- / gehosteter Server |
Node.js 18+
Ein RapidAPI-Schlüssel mit abonniertem Geomelon-API-Zugang
Related MCP server: bamwor-mcp-server
Kopieren Sie .env.example nach .env und tragen Sie Ihren Schlüssel ein:
cp .env.example .envGEOMELON_API_KEY=your_rapidapi_key_here
PORT=3000 # HTTP transport onlyFügen Sie dies zu ~/Library/Application Support/Claude/claude_desktop_config.json hinzu:
{
"mcpServers": {
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}
}Fügen Sie dies zur MCP-Konfiguration Ihres Editors hinzu (der genaue Pfad variiert je nach Editor):
{
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}Starten Sie den Server:
GEOMELON_API_KEY=your_key PORT=3000 npx geomelon-mcp-httpVerweisen Sie dann Ihren MCP-Client auf http://your-host:3000/mcp.
Der HTTP-Transport ist zustandslos – jede Anfrage ist unabhängig, es müssen keine Sitzungen verwaltet werden.
Tool | Beschreibung |
| Suche nach Name, Ländercode, Region, Bevölkerungsbereich, Sortierreihenfolge |
| Vollständige Details für eine Stadt per UUID |
| Städte in der Nähe eines Breitengrads/Längengrads, sortiert nach Entfernung |
| Größte Städte in der Nähe eines Breitengrads/Längengrads, sortiert nach Bevölkerung |
| Entfernung in km zwischen zwei Städten |
Tool | Beschreibung |
| Alle Länder auflisten, Filter nach Telefonvorwahl |
| Vollständige Details für ein Land per UUID (einschließlich Übersetzungen und Regionen) |
Tool | Beschreibung |
| Regionen auflisten, Filter nach Länder-UUID |
| Vollständige Details für eine Region per UUID |
Tool | Beschreibung |
| Alle Sprachen in der Datenbank auflisten |
| Details für eine Sprache per UUID |
npm install
npm run build # compile TypeScript → dist/Starten Sie den stdio-Server direkt:
GEOMELON_API_KEY=your_key node dist/stdio.jsStarten Sie den HTTP-Server direkt:
GEOMELON_API_KEY=your_key PORT=3000 node dist/http.jsSearch cities using a country name instead of an ISO code. Resolves the country first, then searches cities within it.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | City name prefix to filter by | |
| sort | No | Sort order | |
| limit | No | Max results (default 20) | |
| offset | No | Pagination offset | |
| countryName | Yes | Country name prefix (e.g. "France", "United States") | |
| maxPopulation | No | Maximum population | |
| minPopulation | No | Minimum population | |
| preferredLanguages | No | Comma-separated BCP 47 language tags |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so the description's mention of 'Resolves the country first' adds some behavioral context but does not provide additional safety or limitation details. Description does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences that directly describe the tool's core purpose without any redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description gives a high-level overview of the two-step process (resolve country, search cities) but does not mention pagination or return format despite pagination parameters existing. Adequate but could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all parameters are described there. The description does not add meaning beyond the schema, but baseline is 3 due to high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'search' and resource 'cities', and specifies the mechanism: using a country name instead of an ISO code. It distinguishes the tool's function clearly despite no siblings listed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for searching cities by country name (as opposed to ISO code), providing some context. However, it does not explicitly state when to use or avoid this tool, nor does it reference alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.1cities_by_coordinates_closestcities_by_coordinates_largestcities_distancecity_contextcompare_citiescountry_overviewfind_cities_near_cityget_cityget_city_settlement_typesget_city_translationsget_countryget_country_regionsget_country_translationsget_languageget_regionget_region_translationslist_countrieslist_languageslist_regionssearch_citiesv1.0.9cities_by_coordinates_closestcities_by_coordinates_largestcities_distancecity_contextcompare_citiescountry_overviewfind_cities_near_cityget_cityget_city_settlement_typesget_city_translationsget_countryget_country_regionsget_country_translationsget_languageget_regionget_region_translationslist_countrieslist_languageslist_regionssearch_citiessearch_cities_in_countrycities_by_coordinates_closestcities_by_coordinates_largestcities_distancecity_contextcompare_citiescountry_overviewfind_cities_near_cityget_cityget_city_settlement_typesget_city_translationsget_countryget_country_regionsget_country_translationsget_languageget_regionget_region_translationslist_countrieslist_languageslist_regionssearch_citiessearch_cities_in_countryv1.0.8cities_by_coordinates_closestcities_by_coordinates_largestcities_distancecity_contextcompare_citiescountry_overviewfind_cities_near_cityget_cityget_city_settlement_typesget_city_translationsget_countryget_country_regionsget_country_translationsget_languageget_regionget_region_translationslist_countrieslist_languageslist_regionssearch_citiessearch_cities_in_countryScored across 1 tool
With only one tool, there is no risk of confusion or overlap with other tools.
The single tool name follows a clear verb_noun pattern (search_cities_in_country), which is consistent and descriptive.
A single tool feels thin for a geographic data server; while it serves a specific purpose, users might expect more capabilities like listing countries or city details.
The tool only allows searching cities by country name, missing essential operations like retrieving city details, listing countries, or reverse lookups, making the surface severely incomplete.
Geo-based flight search MCP server. Find more flights between any two places on earth
Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries.
MCP server for Japan geodata: cadastral lot numbers (chiban) and reverse geocoding, for AI agents.
Geospatial AI MCP server — satellite imagery, embeddings, weather, GNS governance
