Integration

IP2Location.io integration

IP2Location.io looks up an IPv4 or IPv6 address and returns its country, region, city, coordinates, ZIP code, time zone, ASN and proxy flag on every plan. Higher plans add ISP, domain, usage type and weather station (Starter), continent, country, region and time zone objects and mobile carrier data (Plus), then AS details, proxy and threat flags, a fraud score, the IAB ad category and the district (Security). Fields outside the plan are absent from the answer. It also lists the domain names hosted on an IP address (reverse IP, the IP2WHOIS Hosted Domain lookup), page by page. The bulk lookup (a paid-plan route answering an object keyed by each IP address) and the XML response format are not included; the domain WHOIS lookup is the separate IP2WHOIS integration. Authentication is an IP2Location.io API key, sent as the key query parameter; the same key serves the hosted domain lookup and also works for the IP2WHOIS integration, so save it in both. A free plan gives 50,000 queries per month.

Connect IP2Location.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with IP2Location.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.

Hosted domain, 1 operation

list_hosted_domainsList hosted domainsGETLists the domain names hosted on an IPv4 or IPv6 address, one page at a time, with total_domains and total_pages. Pass page to read the next pages (the vendor's example shows 100 domains per page).

Ip address, 1 operation

lookup_ip_locationLookup ip locationGETGeolocates an IPv4 or IPv6 address: country, region, city, latitude and longitude, ZIP code, time zone, ASN and is_proxy. Higher plans add ISP and usage type (Starter), location objects (Plus), proxy details and fraud_score (Security).

Use IP2Location.io from Claude Code, Cursor or Codex

Connect IP2Location.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its IP2Location.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 IP2Location.io

Create your workspace
Sign up free. Nothing to install.
Connect IP2Location.io once
Add your IP2Location.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.