Integration

Connect Request Tracker (RT) to GeoNames

When Ticket Created fires in Request Tracker (RT), your agent runs Address reverse geocoding in GeoNames. Describe the whole flow and it is built, tested on every scenario and kept running.

Request Tracker (RT)3 triggersRequest Tracker (RT)19 actionsGeoNames42 actions

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 Request Tracker (RT) and GeoNames to do together?

Ask the assistant

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

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)

Example flows

What Request Tracker (RT) can start in GeoNames

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 Request Tracker (RT) and GeoNames

Triggers and actions 3 triggers ยท 61 actions

Each app on its own

Reviews

What our customers say

More from Request Tracker (RT)

More into GeoNames

Questions

Request Tracker (RT) and GeoNames, answered

What can start an automation from Request Tracker (RT)?

Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.

What can your agent do in GeoNames when something happens in Request Tracker (RT)?

Any of GeoNames's 42 actions, including Address reverse geocoding, Contains, Country code from coordinates and Country subdivision. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from GeoNames to Request Tracker (RT)?

GeoNames has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads GeoNames's API documentation and adds it.

Do I have to build a connector for Request Tracker (RT) or GeoNames?

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.