Ipgeolocation Io MCP Server

Official MCP server for IP geolocation, IP security, abuse contacts, ASN, timezone, astronomy, and user-agent parsing. That is what the ipgeolocation io mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Official MCP server for IPGeolocation.io. Includes 16 MCP tools: IP geolocation, threat/VPN/proxy detection, timezone lookups and conversions, sunrise/sunset/moon data, ASN details, abuse contacts, and user-agent parsing. Seven tools work on the free plan (1,000 credits/day). Paid plans unlock all 16 plus bulk endpoints (up to 50,000 items per call; default 1,000, configurable via IPGEOLOCATION_MCP_MAX_BULK_ITEMS).

The tools it exposes

The server publishes 14 tools. What each one is for:

• Requirements — get_my_ip works without an API key. Everything else requires one
• Cline — Open MCP Servers panel > Configure > Advanced MCP Settings. Add to cline_mcp_settings.json:
• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Glama — You can try the server on Glama directly. Only IPGEOLOCATION_API_KEY is required
• lookup_ip — Use this when you need location, timezone, currency, or ASN for one IP address. On paid plans you can add include modules to pull security, abuse, or
• bulk_lookup_ip — Takes an array of IPs or domains (up to 1,000 by default, configurable with IPGEOLOCATION_MCP_MAX_BULK_ITEMS). Supports the same include, fields, and
• get_my_ip — Returns the public IP of the machine running the server. Free. 0 credits. No API key needed.
• check_security — Returns threat score, VPN/proxy/Tor flags, provider names, confidence scores, bot/spam indicators, anonymity flags, and cloud-provider status
• bulk_security_check — Batch version of check_security. Paid. 2 credits per IP.
• get_timezone — Current time and timezone details for a location. Free and paid. 1 credit.
• convert_timezone — Converts a time between two locations. Free and paid. 1 credit.

What it needs from you

Configuration is passed through the environment: IPGEOLOCATION_API_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 22 or later - npx available in your terminal - An IPGeolocation.io API key for most tools get_my_ip works without an API key. Everything else requires one. Sign up for a free IPGeolocation API key

Getting it running

ipgeolocation-io-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ipgeolocation Io MCP's toolset — Requirements, Cline, Cursor and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ipgeolocation; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• 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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ipgeolocation Io MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.