Integration

Connect Chaport to keycdn IP Location Finder

When something happens in Chaport, your agent does the next thing in keycdn IP Location Finder. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Chaport and keycdn IP Location Finder to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Chaport tells you who is chatting; keycdn IP Location Finder tells you where they are connecting from. Joining them means a visitor's city, country, timezone and ISP can be looked up as soon as they appear or start a chat, and written back onto the Chaport visitor record so operators read it before replying.

Example flows

What Chaport can start in keycdn IP Location Finder

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Chaport and keycdn IP Location Finder

Triggers and actions 8 triggers · 13 actions

Each app on its own

Reviews

What our customers say

More from Chaport

More into keycdn IP Location Finder

Questions

Chaport and keycdn IP Location Finder, answered

Where does the location data end up in Chaport?

The lookup result from keycdn IP Location Finder can be written onto the visitor with the Update a Visitor action, which fills notes and custom data fields while leaving anything you skip untouched. You can also post it into the chat with Send a Message.

Can it run on an existing chat rather than a brand new visitor?

Yes. Triggers such as New Chat Started, New Message Sent, Chat Closed and Visitor Updated all work as the starting point for a Find IP location lookup, and the agent tests every scenario before it goes live.

What can start an automation from Chaport?

Any of Chaport's 8 triggers in the catalog, including Chat Closed (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.

What can your agent do in keycdn IP Location Finder when something happens in Chaport?

Any of keycdn IP Location Finder's 1 action, including Find IP location. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from keycdn IP Location Finder to Chaport?

keycdn IP Location Finder has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads keycdn IP Location Finder's API documentation and adds it.

Do I have to build a connector for Chaport or keycdn IP Location Finder?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.