Geolocation MCP Server

Geolocation Ai automation via MCP. Includes geolocate ip, calculate distance, parse coordina... The geolocation mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

MEOK AI Labs — IP geolocation, distance calculation, and coordinate operations.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Its toolset

Everything the assistant can do here goes through one of these:

• Well — documented API
• Production-ready — Active maintenance
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the geolocation mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Geolocation's toolset — Well, Production-ready, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by CSOAI-ORG; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.