Build solutions, not workarounds.
What do you want Felt and Intervals 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 Intervals
When New or updated map in Felt
then Add client in Intervals
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 Intervals
Triggers and actions 7 triggers · 38 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.
- New client
Polling trigger: fires when a new client is created in Intervals.
- New invoice
Polling trigger: fires when a new invoice is created in Intervals.
- New milestone
Polling trigger: fires when a new milestone is created in Intervals.
- New person
Polling trigger: fires when a new person is added in Intervals.
- New project
Polling trigger: fires when a new project is created in Intervals.
- New task
Polling trigger: fires when a new task is created in Intervals.
- Add client
Create a new client.
- Add expense
Create a new expense.
- Add invoice
Create a new invoice.
- Add milestone
Create a new milestone.
- Add person
Create a new person (team member).
- Add project
Create a new project.
- Add task
Create a new task.
- Add time entry
Log a new time entry against a task.
- Add timer
Start a new timer for a task.
- Delete client
Delete a client.
- Delete expense
Delete an expense.
- Delete invoice
Delete an invoice.
- Delete milestone
Delete a milestone.
- Delete person
Delete a person.
- Delete project
Delete a project.
- Delete task
Delete a task.
- Delete time entry
Delete a logged time entry.
- Delete timer
Delete a timer.
- Get client
Retrieve a single client by id.
- Get expense
Retrieve a single expense by id.
- Get invoice
Retrieve a single invoice by id.
- Get milestone
Retrieve a single milestone by id.
- Get person
Retrieve a single person by id.
- Get project
Retrieve a single project by id.
- Get task
Retrieve a single task by id.
- Get time entry
Retrieve a single logged time entry by id.
- Get timer
Retrieve a single timer by id.
- List milestones
Retrieve all milestones in the Intervals account.
- List tasks
Retrieve all tasks in the Intervals account.
- Update client
Update an existing client's details.
- Update expense
Update an existing expense.
- Update invoice
Update an existing invoice.
- Update milestone
Update an existing milestone.
- Update person
Update an existing person's details.
- Update project
Update an existing project's details.
- Update task
Update an existing task's details.
- Update time entry
Update an existing logged time entry.
- Update timer
Update a timer (e.g. stop or adjust it).
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 Intervals
Google Calendar to IntervalsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
QuickBooks Online to IntervalsQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
ActiveCampaign to IntervalsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Felt and Intervals, 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 Intervals when something happens in Felt?
Any of Intervals's 38 actions, including Update client, Update expense, Update invoice and Update milestone. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Intervals to Felt?
Intervals has no triggers in the catalog today, so automations start in Felt. If you need the other direction, ask: your agent reads Intervals's API documentation and adds it.
Do I have to build a connector for Felt or Intervals?
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.