Build solutions, not workarounds.
What do you want Quo and Ecal to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Quo can start in Ecal
When List Phone Numbers in Quo
then Add event in Ecal
When List Phone Numbers in Quo
then Update event in Ecal
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 Quo and Ecal
Triggers and actions 1 trigger · 30 actions
Trigger
List Phone NumbersTriggers when a new phone number is added to your Quo workspace.
Action
Add contactAdds a new contact to your Quo workspace, with name, company, role, emails, phone numbers and custom field values.
Action
Add taskCreates a task in Quo linked to a phone number, a conversation, or a conversation activity, optionally with a due date and an assigned user.
Action
Delete contactDeletes a contact from your Quo workspace.
Action
Get a Message by IDReturns a single text message by its ID, including its sender, recipients, content, direction, delivery status and any attached media.
Action
Get a Summary for a CallReturns the AI-generated summary of a call, including key points discussed, suggested next steps, and any Sona job results. Call summaries are available on Business and Scale plans.
Action
Get a Transcription for a CallReturns the transcript of a call, including each spoken segment with its speaker and timing. Transcripts are available on Quo Business and Scale plans.
Action
Get callReturns a single Quo call by its ID, including its direction, status, participants, duration and timestamps.
Action
Get contactReturns a single Quo contact by its ID, including name, company, role, phone numbers, emails and custom field values.
Action
Get phone numberReturns one of your Quo phone numbers, including its display name, number, forwarding setting, assigned users and calling/messaging restrictions.
Action
Get Recordings for a CallReturns the recordings for a call, oldest segment first, with each recording's status, duration, file type and download URL.
Action
Get userReturns a user in your Quo workspace, including their name, email, role and profile picture.
Action
Get voicemail for a callReturns the voicemail left on a call, including its status, length, transcript and a link to the audio. Fields stay blank while the voicemail is still processing.
Action
List CallsReturns the calls between one of your Quo numbers and a specific external phone number, optionally limited to a date range.
Action
List contactsReturns the contacts in your Quo workspace, optionally limited to contacts with specific external IDs or sources.
Action
List ConversationsReturns the conversations in your Quo workspace, newest activity first, optionally narrowed to specific Quo numbers, a user's access, or a created/updated date range.
Action
List MessagesReturns the text messages exchanged between one of your Quo numbers and the given participants, newest first, optionally filtered by sender and date range.
Action
List Phone NumbersReturns the phone numbers in your Quo workspace along with the users who have access to each, optionally limited to one user's numbers.
Action
List tasksReturns the tasks in your Quo workspace, including title, description, due date, assignee and completion status.
Action
List usersReturns every user in your Quo workspace, with their email, name, role and picture.
Action
Send a MessageSends a text message from one of your Quo phone numbers to up to 10 recipients.
Action
Update contactUpdates an existing Quo contact's name, company, role, emails, phone numbers and custom fields. Fields you leave blank keep their current values.
Action
Add calendarCreates a new calendar in your ECAL account.
Action
Add eventCreates a new event in an ECAL calendar.
Action
Delete calendarDeletes a calendar along with all of its events and event history.
Action
Delete eventDeletes an event, by its id or reference, from an ECAL calendar.
Action
Get calendarReturns a single ECAL calendar and its full details, looked up by its id or reference.
Action
Get eventReturns a single ECAL event and its full details, looked up by event id or your own event reference.
Action
List calendarsReturns the list of calendars on your ECAL account, optionally including draft calendars.
Action
Update calendarUpdates an existing ECAL calendar's name, categories, reference, genre, note, logo or draft status. Fields left blank are unchanged.
Action
Update eventUpdates an existing ECAL event, identified by its id or your own reference. Only the fields you fill in are changed.
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 Quo
Quo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Quo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Quo to StripeStripe is a payment processing platform for online businesses.
Quo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Quo to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Quo to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Ecal
Google Sheets to EcalGoogle Sheets
HubSpot to EcalHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to EcalSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to EcalSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gmail to EcalGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to EcalGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Quo and Ecal, answered
What can start an automation from Quo?
Any of Quo's 1 trigger in the catalog, including List Phone Numbers. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ecal when something happens in Quo?
Any of Ecal's 9 actions, including Update calendar, Update event, Add calendar and Add event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ecal to Quo?
Ecal has no triggers in the catalog today, so automations start in Quo. If you need the other direction, ask: your agent reads Ecal's API documentation and adds it.
Do I have to build a connector for Quo or Ecal?
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 Quo and Ecal without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app 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.