Ip2location Geolocation
Let your coding agent resolve visitor IPs into country, city, timezone, and ISP without leaving the chat.
Overview
com.mcparmory/ip2location-geolocation is a MCP server for the Grow phase that looks up IP addresses and returns geolocation fields such as country, city, timezone, and ISP.
What is this MCP server?
- Resolves IP addresses to country, city, timezone, and ISP via MCP tools
- Ships as stdio MCP with uvx (PyPI) or Docker OCI package at version 1.0.3
- Fits fraud review, geo-aware UX, and log enrichment workflows
- Published through the mcparmory registry with GitHub source
- No custom skill file—direct Model Context Protocol server integration
- Server version 1.0.3
- 2 distribution options: PyPI uvx and OCI Docker
- Stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
You have raw IPs in logs or signups but no quick way for your agent to turn them into readable location context.
Who is it for?
Indie SaaS founders who want agent-driven IP enrichment during analytics reviews or lightweight fraud checks.
Skip if: Teams that need offline MaxMind databases, bulk batch ETL, or enterprise SIEM-grade geo threat feeds without the IP2Location stack.
What do I get? / Deliverables
Your agent can geolocate IPs on demand so you can segment users, triage abuse, and explain traffic without manual API scripting.
- Structured geolocation fields for a queried IP address
- Agent-accessible lookup tools without a custom script
- Repeatable IP enrichment during analytics or support workflows
Recommended MCP Servers
Journey fit
Geolocation lookups usually happen after you have traffic or logs and need to segment or explain behavior by region. Analytics is the canonical shelf for enriching IPs with location metadata for dashboards, support, and funnel breakdowns.
How it compares
MCP geolocation integration, not a standalone analytics dashboard or agent skill.
Common Questions / FAQ
Who is com.mcparmory/ip2location-geolocation for?
Solo and indie builders who use AI coding agents and need IP location details while working on growth, security, or support tasks.
When should I use com.mcparmory/ip2location-geolocation?
Use it when you are analyzing signups, logs, or support tickets and want country, city, timezone, or ISP data resolved from an IP inside your agent session.
How do I add com.mcparmory/ip2location-geolocation to my agent?
Register the stdio server in your MCP client using the mcparmory-ip2location-geolocation uvx package or the ghcr.io/mcparmory/ip2location-geolocation:1.0.3 Docker image, then restart the agent.