io.github.wtronk/geolocation-mcp
Geolocation tools (reverse geocoding, ip lookup, etc) using Jeleo Geolocation API
What can you do with io.github.wtronk/geolocation-mcp?
reverse_geocode: Get rich location metadata (city, country, population metrics, economic data) from latitude/longitude coordinates.batch_reverse_geocode: Resolve a list of multiple geographic coordinates in a single request.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ghcr.io/wtronk/geolocation-mcp:v1.0.0claude mcp add geolocation-mcp -e 'YOUR_API_KEY=<your your_api_key>' -e 'JELEO_API_URL=https://www.jeleo.zone.id/api/geolocation' -- docker run -i --rm ghcr.io/wtronk/geolocation-mcp:v1.0.0
{
"mcpServers": {
"geolocation-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wtronk/geolocation-mcp:v1.0.0"
],
"env": {
"YOUR_API_KEY": "<your your_api_key>",
"JELEO_API_URL": "https://www.jeleo.zone.id/api/geolocation"
}
}
}
}
Environment variables
YOUR_API_KEYrequired secret Your API key for the serviceJELEO_API_URLBase URL for the Jeleo Geolocation API
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
geolocation-mcp
This is a Model Context Protocol (MCP) server that acts as a wrapper around the GeoLocation API. It provides tools for LLMs (like Claude) to perform fast reverse geocoding and batch reverse geocoding (via IP and coordinates).
Tools
reverse_geocode: Get rich location metadata (city, country, population metrics, economic data) from latitude/longitude coordinates.batch_reverse_geocode: Resolve a list of multiple geographic coordinates in a single request.
Configuration
The MCP server requires an API Key and an API Base URL. You can retrieve them from https://jeleo.zone.id/. They are provided to the server as command-line arguments:
-apikey: Your Jeleo API Key-url: Base URL for the Jeleo API (default:https://www.jeleo.zone.id/api/geolocation)
Building and Running Locally
The server runs on standard input/output (stdio), which is standard for MCP. It's designed to be run as an executable or via Docker.
Using Docker (Recommended for Registry)
To build the Docker image:
docker build -t geolocation-mcp .
To run it locally via Docker:
docker run -i --rm geolocation-mcp -apikey YOUR_API_KEY
Direct Execution
If you have Go installed, you can build and run it directly:
go build -o geolocation-mcp main.go
./geolocation-mcp -apikey YOUR_API_KEY
Adding to an MCP Client (e.g. Claude Desktop)
If you have published the image to a container registry, or just using it locally, add it to your claude_desktop_config.json:
Local Docker:
{
"mcpServers": {
"geolocation": {
"command": "docker",
"args": ["run", "-i", "--rm", "geolocation-mcp", "-apikey", "YOUR_API_KEY", "-url", "https://www.jeleo.zone.id/api/geolocation"]
}
}
}
Frequently asked questions
What is io.github.wtronk/geolocation-mcp?
Geolocation tools (reverse geocoding, ip lookup, etc) using Jeleo Geolocation API
How do I install io.github.wtronk/geolocation-mcp?
It runs on your machine. In Claude Code: claude mcp add geolocation-mcp -e 'YOUR_API_KEY=<your your_api_key>' -e 'JELEO_API_URL=https://www.jeleo.zone.id/api/geolocation' -- docker run -i --rm ghcr.io/wtronk/geolocation-mcp:v1.0.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.wtronk/geolocation-mcp need an API key?
Yes. It expects YOUR_API_KEY, which you set in its configuration.
Is io.github.wtronk/geolocation-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.wtronk/geolocation-mcp?
It is published by wtronk. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.