Integration

Ip2Geo integration

Ip2Geo converts IPv4 and IPv6 addresses into geolocation data: continent, country, subdivision, city, coordinates, postal code, time zone, flag, currency, registered country and ASN. Convert one address, or up to 5,000 in one request, then read back the conversions your project made (one by id, up to 100 by id, or a page of the list) over the current month and the twelve before it. Every address sent counts toward the plan's monthly conversion quota (1,000 on Free, 10,000 on Starter, 100,000 on Growth, unlimited on Scale), valid or not; a project over its quota gets HTTP 429 on every operation. Authentication is an Ip2Geo secret key (i2g_sk_...) sent in the x-api-key header; use the secret key here. A public key (i2g_pk_...) is meant for browsers: it only works when the request's Origin header matches the domain it was registered for, only converts addresses, and is refused with HTTP 403 when reading conversions.

Connect Ip2Geo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ip2Geo.Built from the 5 Ip2Geo tools below, on the connection you add once.

What you can do with Ip2Geo

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.

Conversion, 3 operations

get_conversionGet conversionGETRetrieves one of your project's stored conversions by its uniqueId (from list_conversions). Ids older than the current month and the twelve before it, unknown or another project's answer 404. Needs a secret key.
get_conversionsGet conversionsPOSTRetrieves up to 100 of your project's conversions by their uniqueId. Unknown, foreign or expired ids are left out and rows are not in the order asked, so match them by uniqueId. Needs a secret key.
list_conversionsList conversionsGETLists your project's conversions, newest first, in pages of up to 50 (offset and limit), over the current month and the twelve before it; hasMore and totalCount drive paging. Filter by address with ipSearch. Needs a secret key.

Ip address, 2 operations

convert_ipConvert ipGETConverts one IPv4 or IPv6 address into its geolocation data (continent, country, subdivision, city, coordinates, time zone, currency, ASN). Counts toward the quota, valid or not; an address with no record (private, reserved) answers 404.
convert_ipsConvert ipsPOSTConverts up to 5,000 IPv4 or IPv6 addresses in one request; data holds one item per address, in the order sent, with conversion null for an invalid address or one without a geolocation record. Every address counts toward the quota.

Use Ip2Geo from Claude Code, Cursor or Codex

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

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