Skip to main content

IP2Location.io IP Geolocation MCP Server

Base URL: https://api.ip2location.io

Category Maps & Location
Tools 1
Auth API Key

API Info


Install

Quick Start (recommended)

API_KEY=YOUR_API_KEY \
uvx mcparmory-ip2location-geolocation

With pip

pip install mcparmory-ip2location-geolocation
API_KEY=YOUR_API_KEY \
mcparmory-ip2location-geolocation

MCP Client Configuration

Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):

{
  "mcpServers": {
    "ip2location-geolocation": {
      "command": "uvx",
      "args": ["mcparmory-ip2location-geolocation"],
      "env": {
        "API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Credentials

Set the following environment variables (via MCP client env config, shell export, or .env file):

  • API_KEY — API Key Authentication (key)

Do not commit credentials to version control.


Run Locally

First, configure your credentials in .env (see Credentials above).

pip install -r requirements.txt
python server.py

Connect MCP Client

Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.

Example (if server is at /home/user/mcp-servers/ip2location-geolocation):

{
  "mcpServers": {
    "ip2location-geolocation": {
      "command": "python",
      "args": ["/home/user/mcp-servers/ip2location-geolocation/server.py"]
    }
  }
}

Docker

Pre-built image (recommended)

docker run -p 8000:8000 \
  -e API_KEY=YOUR_API_KEY \
  ghcr.io/mcparmory/ip2location-geolocation:latest

Build from source

First, configure your credentials in .env (see Credentials above).

docker build -t ip2location-geolocation .
docker run -p 8000:8000 --env-file .env ip2location-geolocation

Before running, make sure ports 8000 are free.### MCP client config (Docker)

For Docker, use SSE transport in your MCP client config:

{
  "mcpServers": {
    "ip2location-geolocation": {
      "type": "sse",
      "url": "http://localhost:8000/sse"
    }
  }
}

Files

  • .env - Credentials and server configuration
  • .mcp.json - MCP client config template
  • Dockerfile - Container build
  • LICENSE - MIT license for this generated code
  • requirements.txt - Python dependencies
  • README.md - This file
  • server.py - MCP server entry point
  • _auth.py - Authentication handlers
  • _models.py - Request/response models
  • _validators.py - Input validation

Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.


MCP Blacksmith
Generated by MCP Blacksmith · Quickstart docs · Report a bug

Metadata

Release files for mcparmory-ip2location-geolocation 1.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for mcparmory-ip2location-geolocation 1.0.3
File Interpreter ABI Platform Actions
mcparmory_ip2location_geolocation-1.0.3-py3-none-any.whl Python 3 none any Details for mcparmory_ip2location_geolocation-1.0.3-py3-none-any.whl

Release files / mcparmory_ip2location_geolocation-1.0.3-py3-none-any.whl

Download URL mcparmory_ip2location_geolocation-1.0.3-py3-none-any.whl
Size 35.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
83677e5a1bee4e6fb4da73f6b377e23dfdd953e518340d5b321a9b5b86037332
BLAKE2b-256 checksum
How to use checksums
00698e7289a6c62333021574c12070010af4a455ccec65703c2d06264ba1212e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.3

Security for mcparmory-ip2location-geolocation 1.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page