Integration

IPGeolocation.io integration

IPGeolocation.io answers questions about IP addresses, places and time: geolocation, ASN, currency and time zone of an IPv4 or IPv6 address, threat and VPN or proxy signals, abuse contacts, Autonomous System details, the current time zone of a place or airport and time conversion between two places, sunrise, sunset and moon data for a place and date, and parsing of user agent strings. The free plan covers single IP geolocation, time zone and astronomy lookups; security, abuse contact, ASN, user agent, domain and bulk lookups (up to 50,000 entries) need a paid plan. The route that returns the caller's own IP, the user agent route that parses the request's own header, and XML output are not exposed. Authentication is an API key sent as the apiKey query parameter.

Connect IPGeolocation.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in IPGeolocation.io.Built from the 12 IPGeolocation.io tools below, on the connection you add once.

What you can do with IPGeolocation.io

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Abuse, 1 operation

lookup_ip_abuse_contactLookup ip abuse contactGETReturns who handles abuse reports for an IPv4 or IPv6 address: route, organization, contact name and kind, emails, phone numbers and postal address. Paid plans only, 1 credit per lookup.

Asn, 1 operation

lookup_asnLookup asnGETReturns an Autonomous System by ASN (asn) or by the IPv4 or IPv6 address it routes (ip): organization, country, type, domain, registry and route counts; include adds peers, upstreams, downstreams, routes and WHOIS. Paid plans only.

Astronomy, 1 operation

lookup_astronomyLookup astronomyGETReturns sunrise, sunset, moonrise, moonset, twilight phases, golden and blue hours, solar noon, day length, sun and moon positions and the moon phase for a place (coordinates, address or IP) on a date.

Convert, 1 operation

convert_timezoneConvert timezoneGETConverts a date and time (or now) from a source place to a destination place, each given as an IANA zone, an address, coordinates, an IATA or ICAO airport code, or a UN/LOCODE; returns both times and the difference.

Ipgeo, 1 operation

lookup_ip_geolocationLookup ip geolocationGETLooks up one IPv4 or IPv6 address (a domain name needs a paid plan): location, country metadata, currency, ASN and time zone; paid plans also get network and company, and include adds security, abuse and accuracy modules.

Ipgeo bulk, 1 operation

bulk_lookup_ip_geolocationBulk lookup ip geolocationPOSTLooks up up to 50,000 IPv4 or IPv6 addresses or domain names in one call and returns one geolocation object per entry; invalid, private or bogon entries come back with only a message. Paid plans only.

Security, 1 operation

lookup_ip_securityLookup ip securityGETReturns threat signals for one IPv4 or IPv6 address: a threat score and VPN, proxy, Tor, relay, bot, spam and cloud hosting flags, with provider names, confidence and last-seen dates when known. Paid plans only, 2 credits.

Security bulk, 1 operation

bulk_lookup_ip_securityBulk lookup ip securityPOSTReturns threat signals for up to 50,000 IPv4 or IPv6 addresses in one call, one object per address; invalid, private or bogon addresses come back with only a message. Paid plans only, 2 credits per valid IP.

Time series, 1 operation

lookup_astronomy_time_seriesLookup astronomy time seriesGETReturns one record per day between dateStart and dateEnd (at most 90 days) for a place: sunrise, sunset, moonrise, moonset, twilight phases, solar noon, day length and moon phase.

Timezone, 1 operation

lookup_timezoneLookup timezoneGETReturns the current date, time and time zone details (offsets, DST rules and transitions, abbreviations) for an IANA zone name, coordinates, an address, an IP address, an IATA or ICAO airport code, or a UN/LOCODE.

User agent, 1 operation

parse_user_agentParse user agentPOSTParses one user agent string into the agent's name, type and version, the device (name, type, brand, CPU), the rendering engine and the operating system. Paid plans only.

User agent bulk, 1 operation

parse_user_agent_bulkParse user agent bulkPOSTParses up to 50,000 user agent strings in one call and returns one parsed object per string (agent, device, engine, operating system). Paid plans only, 1 credit per string.

Use IPGeolocation.io from Claude Code, Cursor or Codex

Connect IPGeolocation.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its IPGeolocation.io operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect IPGeolocation.io

Create your workspace
Sign up free. Nothing to install.
Connect IPGeolocation.io once
Add your IPGeolocation.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.