io.github.wtronk/geolocation-mcp

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

0 tools GitHub

No known CVEs

No license

Maintained

Last commit 68d ago

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Maps & Geo

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wtronk-geolocation-mcp)](https://mcppedia.org/s/io-github-wtronk-geolocation-mcp)

Read me

What io.github.wtronk/geolocation-mcp does

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).

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

33/100across 5 weighted dimensions

How we score →

0255075100

−67

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wtronk/geolocation-mcp safe to use?: io.github.wtronk/geolocation-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.wtronk/geolocation-mcp?: io.github.wtronk/geolocation-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.wtronk/geolocation-mcp?: io.github.wtronk/geolocation-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.wtronk/geolocation-mcp actively maintained?: io.github.wtronk/geolocation-mcp is recently maintained — last commit was 68 days ago.

Similar servers

Others in maps

View all →

Tomtom Mcp90

A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.

46 1

io.github.srivastsh/bart-mcp90

Real-time BART departures, trip planning, fares, stations, and advisories.

io.github.vessel-api/vesselapi-mcp88

MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data

dev.forgesworn/rendezvous-mcp87

Fair meeting point discovery for AI agents with isochrone-based travel time fairness

MCP Security Weekly

Get CVE alerts and security updates for io.github.wtronk/geolocation-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

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

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

Is io.github.wtronk/geolocation-mcp safe to use?

io.github.wtronk/geolocation-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.wtronk/geolocation-mcp?

io.github.wtronk/geolocation-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.wtronk/geolocation-mcp?

io.github.wtronk/geolocation-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.wtronk/geolocation-mcp actively maintained?

io.github.wtronk/geolocation-mcp is recently maintained — last commit was 68 days ago.

geolocation-mcp

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