Build solutions, not workarounds.
What do you want Felt and Kloudfox 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)Example flows
What Felt can start in Kloudfox
When New or updated map in Felt
then Add incident in Kloudfox
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 Kloudfox
Triggers and actions 1 trigger · 9 actions
- 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.
- Add incident
Log a new incident against a monitor/resource.
- Add monitor
Create a new uptime/website monitor.
- Delete monitor
Delete a monitor by id.
- Get incident
Retrieve a single incident's details by id.
- Get monitor
Retrieve a single monitor's details by id.
- List incidents
List incidents on the account.
- List monitors
List all monitors on the account.
- List status pages
List status pages on the account.
- Update monitor
Update an existing monitor's configuration (interval, URL, alert settings).
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 capturecapture is a service that is your AI's long-term memory.
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...
More into Kloudfox
Google Calendar to KloudfoxGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Felt and Kloudfox, answered
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 Kloudfox when something happens in Felt?
Any of Kloudfox's 9 actions, including Update monitor, Add incident, Add monitor and Get incident. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Kloudfox to Felt?
Kloudfox has no triggers in the catalog today, so automations start in Felt. If you need the other direction, ask: your agent reads Kloudfox's API documentation and adds it.
Do I have to build a connector for Felt or Kloudfox?
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.