Build solutions, not workarounds.
What do you want Felt and capture to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart 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 maps, adds layers and leaves comments; capture is where notes pile up into morning briefs and action items. Joining them means every map edit, annotation or resolved comment in Felt can be written into capture as a note with the title and details you want, so map work shows up alongside everything else you track.
Example flows
What Felt can start in capture
When New or updated map in Felt
then Add capture in capture
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 capture
Triggers and actions 2 triggers · 1 action
- New or updated map
Fires when a map is created or edited (annotations drawn/edited, layers updated, comments added/resolved). Delivered via Felt's map:update webhook, attached per-map and created in Felt workspace settings UI (no REST endpoint to register it); verify the felt-signature HMAC header. See /rest-api/listening-to-updates-using-webhooks.
- New Capture
Triggers when a new item is saved to your capture library.
- Add capture
Create a new capture.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Felt
Felt to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Felt to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Felt to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Felt to Google SheetsGoogle Sheets
Felt to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Felt to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into capture
ActiveCampaign to captureActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to captureOrganize anything with Airtable, a modern database created for everyone.
Trello to captureTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Asana to captureAsana is a collaborative information manager for workspace.
Brevo to captureBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Felt and capture, answered
Can capture send anything back into Felt?
No. Felt provides the map update trigger, and capture provides the add capture action, so information travels from Felt into capture. Nothing is written back onto the map itself.
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 capture when something happens in Felt?
Any of capture's 1 action, including Add capture. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from capture to Felt?
capture has no triggers in the catalog today, so automations start in Felt. If you need the other direction, ask: your agent reads capture's API documentation and adds it.
Do I have to build a connector for Felt or capture?
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.