Geomelon MCP

What 930m310n/geomelon-mcp MCP server does

930m310n/geomelon-mcp MCP server connects MCP-compatible clients to the Geomelon geographic API. Its tools cover cities, countries, administrative regions, and languages, including multilingual names across 50 languages. City operations include filtered search, UUID-based lookup, translations, settlement classifications, coordinate-based proximity searches, and distance calculations. Country and region tools support listing, UUID lookup, translations, and relationships between countries and their regions.

The server also includes compound operations that combine related requests. These can return a city with its country and region, assemble a country overview with regions and top cities, compare two cities with their distance, find cities near a known city, or search cities using a country name instead of an ISO code.

How it works

930m310n/geomelon-mcp MCP server provides two transports. The geomelon-mcp binary uses stdio for local integrations such as Claude Desktop, Cursor, Windsurf, and Cline. The geomelon-mcp-http binary provides Streamable HTTP for Claude Code and remote clients.

With GEOMELON_API_KEY configured, the server exposes the full set of geographic tools through the Geomelon API. Without that key, it starts in keyless demo mode and exposes only search_cities_autocomplete. That tool uses pre-built static files for country-scoped, language-specific city-name prefix searches and is also available when a key is configured.

The HTTP transport is stateless, so requests do not depend on a persistent session. Its root and /health endpoints return a small status response that indicates whether the instance is running in full or keyless-demo mode. CORS allows browser-based remote MCP clients to reach the HTTP transport.

Setup and configuration

Running the local stdio server requires Node.js 18 or newer. The full configuration needs a RapidAPI key with the Geomelon API subscribed. For Claude Desktop, Cursor, Windsurf, or Cline, configure the npx -y geomelon-mcp command and pass GEOMELON_API_KEY in the MCP server environment.

The same package can run without the key for autocomplete-only use. A public hosted keyless instance is available at https://mcp.geomelon.dev/mcp, so a remote-capable client can use that endpoint without starting a local process or signing up.

For HTTP operation, run npx geomelon-mcp-http. The default MCP endpoint is /mcp on port 3000. Set PORT when another port is needed, and provide GEOMELON_API_KEY for full access. The server loads values from a .env file when run locally or on a hosted machine.

Tools and capabilities

The 930m310n/geomelon-mcp MCP server includes tools for:

• Searching cities by name, country, region, population range, and sort order.
• Looking up city, country, region, and language records by UUID.
• Retrieving translations and settlement classifications.
• Finding nearby or largest cities around coordinates.
• Calculating distance between cities.
• Listing countries by name prefix or telephone dialing code.
• Listing regions for a country and languages in the database.
• Running combined city, country, comparison, and nearby-city queries.
• Performing fast, keyless city autocomplete for supported country and language pairs.

Limitations and notes

Keyless demo mode does not provide the general city, country, region, language, distance, or compound tools; only search_cities_autocomplete is available. Full access depends on a subscribed RapidAPI Geomelon key. The hosted endpoint is likewise limited to the keyless autocomplete tool. HTTP deployments must remain running for clients to connect, and each HTTP request is independent because the transport does not maintain sessions.