Mcp Ip2location Io
Let your agent resolve visitor IPs to country, region, and related geolocation fields via IP2Location.io during app or analytics integration work.
Overview
io.github.ip2location/mcp-ip2location-io is a MCP server for the Build phase that queries IP2Location.io for IP geolocation data through agent-callable tools.
What is this MCP server?
- MCP tools for IP2Location.io geolocation lookups
- Requires IP2LOCATION_API_KEY environment variable
- stdio transport via mcp-ip2location-io PyPI package (v1.1.1)
- Fits personalization, fraud hints, and compliance-aware geo display in apps
- GitHub source: ip2location/mcp-ip2location-io
- Package version 1.1.1; required secret env IP2LOCATION_API_KEY
- stdio transport; PyPI identifier mcp-ip2location-io
- Repository: github.com/ip2location/mcp-ip2location-io
Community signal: 14 GitHub stars.
What problem does it solve?
You need consistent IP-to-location answers inside the agent while building geo features, but manually calling the REST API breaks flow and invites copy-paste errors.
Who is it for?
SaaS and API builders who already use IP2Location.io and want Claude Code or Cursor to help wire geo fields into handlers and tests.
Skip if: Builders who need free IP lookup with no API key or who only want WHOIS domain data instead of IP geolocation.
What do I get? / Deliverables
Geolocation lookups run as MCP tools with your API key configured once, so integration and debugging stay in one agent workspace.
- Agent-invokable IP geolocation queries against IP2Location.io
- Faster integration of geo fields into app code and test scenarios
Recommended MCP Servers
Journey fit
IP geolocation is wired into your product or internal tools during implementation, after you have decided the feature set. This server wraps the IP2Location.io HTTP API behind MCP stdio (mcp-ip2location-io on PyPI), which is a standard third-party API integration task.
How it compares
IP geolocation API MCP wrapper, not a WHOIS domain or free Bing search server.
Common Questions / FAQ
Who is io.github.ip2location/mcp-ip2location-io for?
Indie developers and solo founders integrating IP2Location.io into web apps, agents, or internal tools via MCP.
When should I use io.github.ip2location/mcp-ip2location-io?
Use it while building backend or agent features that need structured geolocation fields from visitor or server IP addresses.
How do I add io.github.ip2location/mcp-ip2location-io to my agent?
Set IP2LOCATION_API_KEY in your MCP server environment, install mcp-ip2location-io from PyPI (v1.1.1), and register the stdio server in your agent’s MCP config.