# How to connect IPGeolocation.io to OpenClaw (paste one key, 13 tools) > Connect IPGeolocation.io to OpenClaw with ClawLink: paste your IPGeolocation.io key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ipgeolocation The usual route to IPGeolocation.io access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical IPGeolocation.io setup: install one ClawHub skill, connect IPGeolocation.io in the browser, and OpenClaw can call real IPGeolocation.io actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to IPGeolocation.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect IPGeolocation.io** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect ipgeolocation # connect IPGeolocation.io (browser OAuth) npx -y @useclawlink/cli actions ipgeolocation # list available actions npx -y @useclawlink/cli run ipgeolocation --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect IPGeolocation.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your IPGeolocation.io API key once. Verify the connection by asking OpenClaw: > Use IPGeolocation.io to bulk lookup ip geolocation and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once IPGeolocation.io is connected in the dashboard, that agent calls the same 13 IPGeolocation.io tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## IPGeolocation.io MCP for OpenClaw Looking for a IPGeolocation.io MCP server for OpenClaw? ClawLink connects IPGeolocation.io to OpenClaw and exposes 13 IPGeolocation.io tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes IPGeolocation.io integration](https://claw-link.dev/hermes/ipgeolocation) works the same way. ## What the OpenClaw IPGeolocation.io integration can do 13 IPGeolocation.io tools are ready for OpenClaw once the account is connected. ### All 13 IPGeolocation.io tools for OpenClaw | Tool | What it does | |---|---| | **Bulk lookup ip geolocation** `ipgeolocation_bulk_lookup_ip_geolocation` | Return geolocation results for 1-50 explicit IP addresses or domains in one paid request | | **Bulk lookup ip security** `ipgeolocation_bulk_lookup_ip_security` | Return threat intelligence for 1-50 IPv4 or IPv6 addresses in one paid request, preserving | | **Bulk parse user agents** `ipgeolocation_bulk_parse_user_agents` | Parse 1-50 custom User-Agent strings in one paid request and return one ordered parser result | | **Convert timezone** `ipgeolocation_convert_timezone` | Convert a supplied or current wall-clock time between two explicit timezone, place, coordinate | | **Get execution egress ip** `ipgeolocation_get_execution_egress_ip` | Return the public IP observed for the Composio execution environment | | **Lookup asn** `ipgeolocation_lookup_asn` | Return detailed autonomous-system metadata for one explicit IP address or ASN number, with | | **Lookup astronomy** `ipgeolocation_lookup_astronomy` | Return Sun, Moon, twilight, golden-hour, and positional data for one explicit location and date | | **Lookup astronomy time series** `ipgeolocation_lookup_astronomy_time_series` | Return daily Sun, Moon, twilight, and golden-hour events for one explicit location over an | | **Lookup ip abuse contact** `ipgeolocation_lookup_ip_abuse_contact` | Return registry abuse contact details for one explicit IPv4 or IPv6 address, including | | **Lookup ip geolocation** `ipgeolocation_lookup_ip_geolocation` | Return location, timezone, currency, ASN, and optional paid enrichments for one explicit IPv4 | | **Lookup ip security** `ipgeolocation_lookup_ip_security` | Return threat score and Tor, proxy, VPN, relay, bot, spam, attacker, and cloud-provider signals | | **Lookup timezone** `ipgeolocation_lookup_timezone` | Return current date, time, UTC offsets, and DST details for one explicit timezone, place | | **Parse user agent** `ipgeolocation_parse_user_agent` | Parse one explicit User-Agent string using the operation available on the free plan | ## Example prompts **Bulk Lookup Ip Geolocation** > Use IPGeolocation.io to bulk lookup ip geolocation and walk me through the result in plain English. **Bulk Lookup Ip Security** > Use IPGeolocation.io to bulk lookup ip security and walk me through the result in plain English. **Bulk Parse User Agents** > Use IPGeolocation.io to bulk parse user agents and walk me through the result in plain English. **Convert Timezone** > Use IPGeolocation.io to convert timezone and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want IPGeolocation.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the IPGeolocation.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected IPGeolocation.io account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for IPGeolocation.io. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right IPGeolocation.io actions to the runtime in a format your agent can reliably use. | 13 tools for IPGeolocation.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes IPGeolocation.io to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect IPGeolocation.io in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the IPGeolocation.io key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the IPGeolocation.io skill but can't call the tools The ClawHub skill teaches OpenClaw about IPGeolocation.io, but the calls run through the ClawLink plugin and your connected account. Make sure IPGeolocation.io is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect IPGeolocation.io from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling IPGeolocation.io tools IPGeolocation.io tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every IPGeolocation.io call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### IPGeolocation.io returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for IPGeolocation.io has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw IPGeolocation.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to IPGeolocation.io: link your IPGeolocation.io account once in the browser and OpenClaw can call the IPGeolocation.io API through 13 ready-made tools — no custom code or token handling. ### How do I add IPGeolocation.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink IPGeolocation.io skill from ClawHub, then you click Connect in the dashboard to authorize IPGeolocation.io. OpenClaw calls the tools from the next message — no config files, and the IPGeolocation.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect IPGeolocation.io to OpenClaw? About two minutes. Sign in, click Connect next to IPGeolocation.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring IPGeolocation.io up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want IPGeolocation.io working from chat. ### OpenClaw installed the IPGeolocation.io skill but can't call the tools The ClawHub skill teaches OpenClaw about IPGeolocation.io, but the calls run through the ClawLink plugin and your connected account. Make sure IPGeolocation.io is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.