Geolocation Mcp

io.github.wtronkPublished by GitHub account wtronkv1.0.0Updated Oct 24, 2026

Geolocation tools (reverse geocoding, ip lookup, etc) using Jeleo Geolocation API

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant turn coordinates into location details and resolve many coordinates at once through the Jeleo Geolocation API.

What you can do
A local stdio MCP server that wraps the Jeleo Geolocation API. It exposes a reverse_geocode tool that returns location metadata such as city, country, population metrics and economic data for a latitude/longitude pair, and a batch_reverse_geocode tool that resolves a list of coordinates in a single request. It is intended for fast reverse geocoding from an assistant.
When to use it
Useful when an assistant needs to label coordinates with place names or other location metadata, or to enrich a list of coordinates in bulk. It fits workflows where reverse geocoding is a recurring step rather than a one-off lookup.
Requirements
Runs locally over stdio, either as a Docker image or a compiled Go binary. Needs a Jeleo API key and the API base URL, passed as the -apikey and -url command-line arguments; the default URL is Network access to the Jeleo service is required.
Before you install
The API key is passed as a plain command-line argument, so it can appear in process listings, shell history and client configuration files; treat it as a secret. Coordinate data is sent to the third-party Jeleo service. The server is read-only and does not write or delete data.

Installation

In SourceWeft

  1. Open Geolocation Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

sh
docker build -t geolocation-mcp .

To run it locally via Docker:

sh
docker run -i --rm geolocation-mcp -apikey YOUR_API_KEY

Direct Execution

If you have Go installed, you can build and run it directly:

sh
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:

json
{  "mcpServers": {    "geolocation": {      "command": "docker",      "args": ["run", "-i", "--rm", "geolocation-mcp", "-apikey", "YOUR_API_KEY", "-url", "https://www.jeleo.zone.id/api/geolocation"]    }  }}

Source: README.md at commit 8d25e94

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.