Geomelon 지리 API를 위한 MCP 서버입니다. 도시, 국가, 지역 및 언어 정보를 MCP 호환 AI 클라이언트가 호출할 수 있는 도구로 제공합니다.
두 가지 전송 방식이 포함되어 있습니다:
바이너리 | 전송 방식 | 사용 사례 |
| stdio | 로컬 클라이언트 — Claude Desktop, Cursor, Cline, Continue |
| HTTP (Streamable) | 원격 / 호스팅 서버 |
Node.js 18 이상
Geomelon API를 구독 중인 RapidAPI 키
Related MCP server: bamwor-mcp-server
.env.example을 .env로 복사하고 키를 입력하세요:
cp .env.example .envGEOMELON_API_KEY=your_rapidapi_key_here
PORT=3000 # HTTP transport only~/Library/Application Support/Claude/claude_desktop_config.json에 추가하세요:
{
"mcpServers": {
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}
}편집기의 MCP 설정에 추가하세요 (정확한 경로는 편집기마다 다름):
{
"geomelon": {
"command": "npx",
"args": ["-y", "geomelon-mcp"],
"env": {
"GEOMELON_API_KEY": "your_rapidapi_key_here"
}
}
}서버 시작:
GEOMELON_API_KEY=your_key PORT=3000 npx geomelon-mcp-http그런 다음 MCP 클라이언트를 http://your-host:3000/mcp로 지정하세요.
HTTP 전송 방식은 상태 비저장(stateless)이므로 각 요청은 독립적이며 관리할 세션이 없습니다.
도구 | 설명 |
| 이름, 국가 코드, 지역, 인구 범위, 정렬 순서로 검색 |
| UUID로 도시의 전체 세부 정보 조회 |
| 위도/경도와 가장 가까운 도시를 거리순으로 조회 |
| 위도/경도 근처의 가장 큰 도시를 인구순으로 조회 |
| 두 도시 간의 거리(km) 계산 |
도구 | 설명 |
| 모든 국가 목록 조회, 전화 국가 번호로 필터링 가능 |
| UUID로 국가의 전체 세부 정보 조회 (번역 및 지역 포함) |
도구 | 설명 |
| 지역 목록 조회, 국가 UUID로 필터링 가능 |
| UUID로 지역의 전체 세부 정보 조회 |
도구 | 설명 |
| 데이터베이스의 모든 언어 목록 조회 |
| UUID로 언어 세부 정보 조회 |
npm install
npm run build # compile TypeScript → dist/stdio 서버 직접 실행:
GEOMELON_API_KEY=your_key node dist/stdio.jsHTTP 서버 직접 실행:
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
