Build solutions, not workarounds.
What do you want Loyverse and Fergus 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 Loyverse can start in Fergus
When Customer Update in Loyverse
then Create Customer in Fergus
When Items Update in Loyverse
then Add Calendar Event in Fergus
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 Loyverse and Fergus
Triggers and actions 3 triggers · 76 actions
Trigger
Customer UpdateTriggers when a customer is updated.
Trigger
Items UpdateTriggers when an item is updated.
Trigger
Receipts UpdateTriggers when a receipt gets created or updated.
Action
Create or Update CategoryCreates or Updates a single category.
Action
Create or Update DiscountCreates or Updates a single discount.
Action
Create or Update ModifierCreates or Updates a modifier.
Action
Create or Update POS DeviceCreates or Updates a single POS device.
Action
Create or Update ReceiptsCreates a receipt
Action
Create or Update Single CustomerCreates or Updates a Single Customer.
Action
Create or Update Single ItemAction
Create or Update SupplierCreates or Updates a single supplier.
Action
Create or Update TaxCreates or Updates a tax.
Action
Create Refund ReceiptCreates a refund receipt. When using the refund API you should take into account these notes: - At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. - Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. - If a refund is created successfully, it will cause a restock of items specified in a refund receipt.
Action
Delete Singe ItemDeletes a single item.
Action
Delete Single CategoryDeletes a single category.
Action
Delete Single CustomerDeletes a single customer.
Action
Delete Single DiscountDeletes a single discount.
Action
Delete Single ModifierDeletes a single Modifier.
Action
Delete Single POS DeviceDeletes a single POS Device.
Action
Delete Single SupplierDeletes a single supplier.
Action
Delete Single TaxDeletes a single tax.
Action
Delete Single VariantDeletes a single variant.
Action
Get List of CategoriesGet list of all categories.
Action
Get List of CustomersGet list of Customers
Action
Get List of DiscountsReturns discounts, most recently created first.
Action
Get List of EmployeesGets a list of employees.
Action
Get List of ItemsGet list of items
Action
Get List of Payment TypesGet list of Payment Types
Action
Get List of POS DevicesThe list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first
Action
Get List of StoresGet list of stores
Action
Get List of SuppliersGets a list of suppliers.
Action
Get List of TaxesGet list of taxes
Action
Get List of VariantsGet lists of item variants.
Action
Get Merchant InformationReturns the business profile of the connected Loyverse merchant account.
Action
Get Single CategoryGet Single Category.
Action
Get Single CustomerGet Single Customer
Action
Get Single DiscountGets a single discount.
Action
Get Single EmployeeGets a single employee.
Action
Get Single ItemGet single item
Action
Get Single ModifierGets a single modifier.
Action
Get Single Payment TypeFetches a payment type by ID. An error occurs if the payment type is not found.
Action
Get Single POS DeviceFetches a POS device by ID. An error occurs if the POS device is not found.
Action
Get Single ReceiptGet a single Receipt.
Action
Get Single StoreGet Single Store
Action
Get Single SupplierFetches a supplier by ID. An error occurs if the supplier is not found.
Action
Get Single TaxGets a single tax.
Action
Get Single VariantGets single item variant.
Action
Update Inventory Levels for ItemsBatch updates Inventory Levels for Item Variants.
Action
Add Calendar EventCreates a new calendar event/booking.
Action
Add ContactCreates a new contact.
Action
Add NoteCreates a new note against a record.
Action
Add QuoteCreates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate.
Action
Add TaskCreates a new task in Fergus, optionally linked to a job and assigned to employees.
Action
Archive SiteArchives a site in Fergus. The site can later be restored.
Action
Create CustomerCreates a new customer.
Action
Create JobCreates a job in Fergus — an active job, a draft job, or a variation of an existing job.
Action
Create SiteCreates a new site.
Action
Delete CustomerDeletes a Fergus customer by ID.
Action
Edit Draft JobUpdates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value.
Action
Finalize Draft JobFinalises a draft job in Fergus, turning it into an active job.
Action
Find All QuotesReturns up to 100 quotes from across all jobs that match the specified status and date criteria.
Action
Find CustomerReturns the customers whose name, or main or billing contact's name, email or phone, contains the search text.
Action
Find SiteFinds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10).
Action
Get Calendar EventReturns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details.
Action
Get ContactReturns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items.
Action
Get Customer by IDReturns a Fergus customer by its ID.
Action
Get Customer InvoiceRetrieves a customer invoice by ID.
Action
Get Job by IDRetrieves a specific job using its unique ID.
Action
Get Quotes for JobReturns all quotes for a Fergus job, optionally filtered by status.
Action
Get Site by IDRetrieves a specific site using its unique ID.
Action
List ContactsLists contacts, with optional filtering.
Action
List Customer InvoicesLists customer invoices, with optional filtering.
Action
List NotesReturns the notes (with their replies) attached to a Fergus record.
Action
List TasksLists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state.
Action
Update ContactUpdates an existing customer contact or site contact in Fergus.
Action
Update CustomerUpdates an existing customer's details.
Action
Update QuoteUpdates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items.
Action
Update SiteUpdates an existing site's details.
Action
Update TaskUpdates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be 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 Loyverse
Loyverse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Loyverse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Loyverse to MailchimpMailchimp marketing automation and email platform.
Loyverse to StripeStripe is a payment processing platform for online businesses.
Loyverse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Loyverse to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Fergus
HubSpot to FergusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FergusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FergusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FergusGoogle Sheets
Gmail to FergusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FergusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Loyverse and Fergus, answered
What can start an automation from Loyverse?
Any of Loyverse's 3 triggers in the catalog, including Customer Update, Items Update and Receipts Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fergus when something happens in Loyverse?
Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fergus to Loyverse?
Fergus has no triggers in the catalog today, so automations start in Loyverse. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it.
Do I have to build a connector for Loyverse or Fergus?
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.