Build solutions, not workarounds.
What do you want Felt and Easybill 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 Easybill
When New or updated map in Felt
then Add customer in Easybill
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 Easybill
Triggers and actions 1 trigger · 14 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 customer
Create a new customer.
- Add document
Create a new document (invoice, quote, etc).
- Add project
Create a new project.
- Add task
Create a new task.
- Add time tracking
Create a new time tracking entry.
- Delete customer
Delete a customer.
- Delete document
Delete a document.
- Get customer
Fetch a single customer by id.
- Get document
Fetch a single document by id.
- List documents
Fetch a list of documents.
- List projects
Fetch a list of projects.
- List tasks
Fetch a list of tasks.
- Update customer
Update an existing customer.
- Update document
Update an existing document.
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 Easybill
Stripe to EasybillStripe is a payment processing platform for online businesses.
Questions
Felt and Easybill, 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 Easybill when something happens in Felt?
Any of Easybill's 14 actions, including Update customer, Update document, Add customer and Add document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Easybill to Felt?
Easybill has no triggers in the catalog today, so automations start in Felt. If you need the other direction, ask: your agent reads Easybill's API documentation and adds it.
Do I have to build a connector for Felt or Easybill?
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.