mcpField
G
geolocation-mcp

geolocation-mcp

Local
github.com/wtronkMaps & Travel0Updated 32w ago
Repository

About geolocation-mcp

geolocation-mcp wraps the Jeleo Geolocation API as an MCP service for LLM applications that need location details from coordinates. It supports single and batch reverse geocoding.

Key features

  1. 01Reverse geocode coordinates
  2. 02Resolve multiple coordinates in batches
  3. 03Return city, country, and location details
  4. 04Include population and economic data

Use cases

  1. 01Enrich records with location details
  2. 02Process geographic coordinates in batches
  3. 03Look up places in LLM workflows

MCP support

It exposes reverse-geocoding and batch reverse-geocoding tools to MCP clients over stdio. A Jeleo API key and base URL are required.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "wtronk-geolocation": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUR_API_KEY",
        "-e",
        "JELEO_API_URL",
        "ghcr.io/wtronk/geolocation-mcp:v1.0.0"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>",
        "JELEO_API_URL": "<JELEO_API_URL>"
      }
    }
  }
}
Run commanddocker run -i --rm -e YOUR_API_KEY -e JELEO_API_URL ghcr.io/wtronk/geolocation-mcp:v1.0.0
Environment variables to set
YOUR_API_KEYSecretYour API key for the service
JELEO_API_URLBase URL for the Jeleo Geolocation API

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/wtronk/geolocation-mcp:v1.0.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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"]
    }
  }
}

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.