Integration

Connect MOCO to ip-api

When New Client fires in MOCO, your agent runs Get IP geolocation in ip-api. 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 MOCO and ip-api 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)

MOCO holds your clients, leads and invoices, while ip-api turns an IP address or domain into a country, city, timezone, ISP and network owner. Connected, a new client or an updated lead in MOCO can be enriched with location details from ip-api, and the result written back as a comment on the MOCO company record.

Example flows

What MOCO can start in ip-api

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 MOCO and ip-api

Triggers and actions 26 triggers · 26 actions

Each app on its own

Reviews

What our customers say

More from MOCO

More into ip-api

Questions

MOCO and ip-api, answered

Can a lookup in ip-api start one of these workflows?

No, ip-api only offers the two lookup actions, so every workflow here begins with a MOCO trigger such as New Company, Updated Lead or New Offer. The ip-api lookup then runs as a step, and anything you want stored goes back into MOCO through actions like Create Comment.

What can I hand to ip-api from a MOCO record?

Get IP geolocation takes a single IP address or domain name, so a website domain or logged IP from the MOCO record works. If you have several hosts to check at once, Get IP geolocations (batch) accepts a list in one request.

What can start an automation from MOCO?

Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Offer and Updated Company. Describe the moment in plain language and your agent picks the right one.

What can your agent do in ip-api when something happens in MOCO?

Any of ip-api's 2 actions, including Get IP geolocation and Get IP geolocations (batch). Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from ip-api to MOCO?

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

Do I have to build a connector for MOCO or ip-api?

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 MOCO and ip-api 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.