Integration

Connect Felt to Mapbox

When New or updated map fires in Felt, your agent runs Get static map image in Mapbox. 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 Felt and Mapbox 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)

Felt is where your team draws and comments on maps; Mapbox is where the geocoding, routing and travel-time work happens. Connecting them means an edit to a Felt map can turn an address into coordinates, pull a route or isochrone, or render a static image in Mapbox without anyone copying points between the two.

Example flows

What Felt can start in Mapbox

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 Felt and Mapbox

Triggers and actions 1 trigger · 8 actions

Each app on its own

Reviews

What our customers say

More from Felt

More into Mapbox

Questions

Felt and Mapbox, answered

What kind of change in Felt can start this?

Felt reports a map as new or updated when annotations are drawn or edited, layers change, or comments are added or resolved. That single event is what the agent listens to, and it can read the map contents to decide whether to call Mapbox at all.

Can the results from Mapbox be written back onto the Felt map?

No, Felt is the trigger side here and has no listed actions, so nothing is written back into the map. The coordinates, routes, isochrones, matrices and static images that Mapbox returns are handed on to whatever you want done with them next.

What can start an automation from Felt?

Any of Felt's 1 trigger in the catalog, including New or updated map. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Mapbox when something happens in Felt?

Any of Mapbox's 8 actions, including Geocode address, Get directions, Get travel time matrix and Optimize route. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Mapbox to Felt?

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

Do I have to build a connector for Felt or Mapbox?

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 Felt and Mapbox without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in Mapbox 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.