Servidor MCP para la API geográfica Geomelon. Expone ciudades, países, regiones e idiomas como herramientas que cualquier cliente de IA compatible con MCP puede invocar.
Se incluyen dos transportes:
Binario | Transporte | Caso de uso |
| stdio | Clientes locales: Claude Desktop, Cursor, Cline, Continue |
| HTTP (Streamable) | Servidor remoto / alojado |
Node.js 18+
Una clave de RapidAPI con la API de Geomelon suscrita
Related MCP server: bamwor-mcp-server
Copia .env.example a .env y rellena tu clave:
cp .env.example .envGEOMELON_API_KEY=your_rapidapi_key_here
PORT=3000 # HTTP transport onlyAñádelo a ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}
}Añádelo a la configuración MCP de tu editor (la ruta exacta varía según el editor):
{
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}Inicia el servidor:
GEOMELON_API_KEY=your_key PORT=3000 npx geomelon-mcp-httpLuego apunta tu cliente MCP a http://your-host:3000/mcp.
El transporte HTTP no tiene estado: cada solicitud es independiente, no hay sesiones que gestionar.
Herramienta | Descripción |
| Buscar por nombre, código de país, región, rango de población, orden de clasificación |
| Detalles completos de una ciudad por UUID |
| Ciudades más cercanas a una latitud/longitud, ordenadas por distancia |
| Ciudades más grandes cerca de una latitud/longitud, ordenadas por población |
| Distancia en km entre dos ciudades |
Herramienta | Descripción |
| Listar todos los países, filtrar por código de marcación telefónica |
| Detalles completos de un país por UUID (incluye traducciones y regiones) |
Herramienta | Descripción |
| Listar regiones, filtrar por UUID de país |
| Detalles completos de una región por UUID |
Herramienta | Descripción |
| Listar todos los idiomas en la base de datos |
| Detalles de un idioma por UUID |
npm install
npm run build # compile TypeScript → dist/Ejecutar el servidor stdio directamente:
GEOMELON_API_KEY=your_key node dist/stdio.jsEjecutar el servidor HTTP directamente:
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
