Integration

IPLocate integration

IPLocate looks up any IPv4 or IPv6 address and returns its geolocation (country, subdivision, city, postal code, coordinates, time zone, currency and calling code, EU membership), its autonomous system and network operator, the company behind the address range, hosting provider details, and privacy and threat flags (VPN, proxy, Tor, iCloud Private Relay, hosting, bogon, abuse blocklist). Use it to localize content, flag anonymous traffic or screen sign-ups. The lookup of the caller's own address and the single-field path filters are not exposed (from LiveContext they would describe its server or return plain text), nor is the batch lookup (its answer is keyed by IP address); abuse contact data and network ranges are not returned. Authentication is an API key from the IPLocate dashboard, sent in the X-API-Key header; a free key allows 1,000 lookups per day (reset 00:00 UTC), paid plans and prepaid credits allow more, every successful lookup counts against the quota, and a 429 answer means the quota is used up. The rate limit is 100 requests per second.

Connect IPLocate How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in IPLocate.Built from the 1 IPLocate tool below, on the connection you add once.

What you can do with IPLocate

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.

lookup_ipLookup ipGETLooks up one IPv4 or IPv6 address: country, city, coordinates, time zone, ASN, company, hosting provider and privacy flags (privacy.is_vpn, is_proxy, is_tor, is_anonymous). Uses one lookup of the quota.

Use IPLocate from Claude Code, Cursor or Codex

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

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