
IP Geolocation MCP By UnClick
Resolve IP addresses to country, city, region, ISP, and timezone—including batch lookups—while implementing geo-aware backend logic with your agent.
Overview
IP Geolocation MCP is a Build-phase MCP server that provides IP-to-location and batch lookup tools with country, city, region, ISP, and timezone for your agent.
What is this MCP server?
- Single and batch IP geolocation lookups
- Returns country, city, region, ISP, and timezone fields
- stdio MCP via @unclick/ipapi-mcp v0.1.0
- UnClick IP Geolocation MCP with npx stdio transport
- Speeds up geo feature prototyping without bespoke HTTP snippets each session
- Server version 0.1.0
- npm package @unclick/ipapi-mcp
- Supports batch IP lookup per catalog description
Community signal: 4 GitHub stars.
What problem does it solve?
Implementing geo-aware backend behavior means repeatedly looking up IPs manually instead of letting the agent test real responses inline.
Who is it for?
Indie SaaS devs wiring localization, signup analytics, abuse heuristics, or support context that needs quick IP enrichment during build.
Skip if: Security teams needing guaranteed bot or VPN classification, legal-grade geofencing audits, or offline MaxMind-only pipelines without external calls.
What do I get? / Deliverables
Your agent can run single or batch IP lookups and embed structured geo fields directly into code, tests, and logging designs.
- Structured IP lookup results with country, city, region, ISP, and timezone
- Batch lookup output for test fixtures or admin tooling
- MCP stdio config snippet for repeatable geo queries in development
Recommended MCP Servers
Journey fit
IP geolocation is backend infrastructure you add when shaping auth, analytics, compliance, or personalization features. Backend is the canonical shelf because lookups feed server-side rules, logging enrichment, and integration code the agent generates.
How it compares
IP lookup MCP integration, not a WAF skill or hosting provider dashboard.
Common Questions / FAQ
Who is IP Geolocation MCP for?
Solo builders implementing backend geo or network context features who want IP lookup tools inside Claude Code, Cursor, or Codex.
When should I use IP Geolocation MCP?
Use it in the Build backend phase when you are coding or testing IP-based locale, ISP, or timezone enrichment in your app or API.
How do I add IP Geolocation MCP to my agent?
Register stdio MCP with identifier @unclick/ipapi-mcp, runtimeHint npx v0.1.0, in your agent MCP config and ensure network access to the geolocation provider the server uses.