Integration

Connect Beanstalk to IP2Location

When New Repository fires in Beanstalk, your agent runs Get my IP details in IP2Location. Describe the whole flow 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 Beanstalk and IP2Location 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

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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)

Beanstalk tells you when a repository or a user appears; IP2Location tells you where an address sits and who registered a domain. Joining them means every new account or repo in Beanstalk can arrive with the geolocation and WHOIS details already looked up, so access reviews and deploy notes start with something to read.

Example flows

What Beanstalk can start in IP2Location

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 Beanstalk and IP2Location

Triggers and actions 2 triggers · 10 actions

Each app on its own

Reviews

What our customers say

More from Beanstalk

More into IP2Location

Questions

Beanstalk and IP2Location, answered

Can IP2Location send anything back into Beanstalk?

IP2Location has no triggers, so it never starts the work; Beanstalk does, through New Repository or New User. After an IP2Location lookup, the agent can still call Beanstalk actions such as Get User, List public keys or List Repositories in the same run.

Where does the IP address for a lookup come from?

It comes from the Beanstalk record you pass in, such as an address stored on the user you fetched with Get User. If no address is available, use Get my IP details in IP2Location, which reports on the address the request itself originates from.

What can start an automation from Beanstalk?

Any of Beanstalk's 2 triggers in the catalog, including New Repository and New User. Describe the moment in plain language and your agent picks the right one.

What can your agent do in IP2Location when something happens in Beanstalk?

Any of IP2Location's 3 actions, including Get my IP details, Lookup domain WHOIS and Lookup IP geolocation. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from IP2Location to Beanstalk?

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

Do I have to build a connector for Beanstalk or IP2Location?

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.

Can my AI client use Beanstalk and IP2Location without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

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.