io.usefulapiPublished by usefulapi.ioOfficial publisherv1.12.4Updated Nov 7, 2026
Read Laudus ERP customers, sales, purchases, stock and accounting reports; create customers.
The publisher's own server: Ably MCP by usefulapi
Hosted MCP server for the Laudus ERP: lets an assistant read customers, sales, purchases, stock and accounting reports, and create customers.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Flaudus/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"laudus-by-usefulapi": {
"type": "http",
"url": "https://laudus.usefulapi.io/mcp"
}
}
}Live endpoint: https://laudus.usefulapi.io/mcp
https://laudus.usefulapi.io/mcp.claude mcp add --transport http laudus https://laudus.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Laudus credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/laudus/
On first connect you will enter your company RUT and the user name and password of a Laudus user with API access. They are validated, stored per-user, and scoped to you. No keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with laudus_upgrade (it returns a Stripe Checkout link). Cancel any time with laudus_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running laudus_upgrade before then undoes the cancel. Or write to [email protected].
MIT
Source: servers/laudus/README.md at commit 4046075
List customers
List customers with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example customerId, name, legalName, VATId, email, phone1, city, county, creditLimit, blocked, customerCategory.name, salesman.name. When a page is full, ask for the next one with offset = offset + limit. POST /sales/customers/list.
limitfieldsfilteroffsetorder_byList sales invoices
List sales invoices and electronic tax documents (facturas, notas de credito) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesInvoiceId, docType.name, docNumber, issuedDate, dueDate, customer.name, customer.VATId, totals.net, totals.total, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /sales/invoices/list.
limitfieldsfilteroffsetorder_byList sales orders
List sales orders (pedidos de venta) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesOrderId, issuedDate, dueDate, customer.name, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /sales/orders/list.
limitfieldsfilteroffsetorder_byList sales quotes
List sales quotes (cotizaciones) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesQuoteId, issuedDate, customer.name, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /sales/quotes/list.
limitfieldsfilteroffsetorder_byList sales receipts
List customer payments received (cobros) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example receiptId, receiptType, issuedDate, dueDate. When a page is full, ask for the next one with offset = offset + limit. POST /sales/receipts/list.
limitfieldsfilteroffsetorder_byList products
List products and services (the item master) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example productId, sku, description, productCategory.name, unitOfMeasure, unitPrice, stockable, discontinued. When a page is full, ask for the next one with offset = offset + limit. POST /production/products/list.
limitfieldsfilteroffsetorder_byList product categories
List product categories with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example productCategoryId, name, fullPath. When a page is full, ask for the next one with offset = offset + limit. POST /production/products/categories/list.
limitfieldsfilteroffsetorder_byList warehouses
List warehouses (bodegas) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example warehouseId, name, city. When a page is full, ask for the next one with offset = offset + limit. POST /production/warehouses/list.
limitfieldsfilteroffsetorder_byList salespeople
List salespeople (vendedores) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesmanId, name. When a page is full, ask for the next one with offset = offset + limit. POST /sales/salesmen/list.
limitfieldsfilteroffsetorder_byList suppliers
List suppliers (proveedores) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example supplierId, name, legalName, VATId, email, phone, city. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/suppliers/list.
limitfieldsfilteroffsetorder_byList purchase invoices
List purchase invoices (facturas de compra) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example purchaseInvoiceId, docNumber, issuedDate, dueDate, supplier.name, totals.total. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/invoices/list.
limitfieldsfilteroffsetorder_byList purchase orders
List purchase orders (ordenes de compra) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example purchaseOrderId, issuedDate, supplier.name, status, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/orders/list.
limitfieldsfilteroffsetorder_byList accounting accounts
List the chart of accounts (plan de cuentas) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example accountId, accountNumber, name. When a page is full, ask for the next one with offset = offset + limit. POST /accounting/accounts/list.
limitfieldsfilteroffsetorder_byList journal entries
List accounting journal entries (comprobantes) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example journalEntryId, journalEntryNumber, date, lines.account.accountNumber, lines.debit, lines.credit. When a page is full, ask for the next one with offset = offset + limit. POST /accounting/journal/entries/list.
limitfieldsfilteroffsetorder_byList cost centers
List cost centers (centros de costo) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example costCenterId, name, code. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/costcenters/list.
limitfieldsfilteroffsetorder_byGet a customer
Get a customer (addresses, contact data, credit limit, category, salesman, price list) by id. GET /sales/customers/{id}.
customer_idrequiredGet a sales invoice
Get a sales invoice with its lines, taxes and totals by id. GET /sales/invoices/{id}.
sales_invoice_idrequiredGet a sales order
Get a sales order with its lines by id. GET /sales/orders/{id}.
sales_order_idrequiredGet a sales quote
Get a sales quote with its lines by id. GET /sales/quotes/{id}.
sales_quote_idrequiredGet a product
Get a product (SKU, description, category, units, prices) by id. GET /production/products/{id}.
product_idrequiredGet a supplier
Get a supplier by id. GET /purchases/suppliers/{id}.
supplier_idrequiredGet a purchase invoice
Get a purchase invoice with its lines by id. GET /purchases/invoices/{id}.
purchase_invoice_idrequiredGet a purchase order
Get a purchase order with its lines by id. GET /purchases/orders/{id}.
purchase_order_idrequiredGet a journal entry
Get an accounting journal entry (comprobante) with its lines by id. GET /accounting/journal/entries/{id}.
journal_entry_idrequiredCustomer pending invoices
Unpaid sales invoices (accounts receivable). Give customer_id for one customer, or leave it out for all customers. GET /sales/customers/{id}/pendingInvoices or /sales/customers/pendingInvoices.
customer_idCustomer credit limit
A customer's credit limit and how much of it is used. GET /sales/customers/{id}/creditLimit.
customer_idrequiredList customer contacts
The contact people of a customer. GET /sales/customers/{id}/contacts.
customer_idrequiredSales invoice receipts
The customer payments (cobros) applied to one sales invoice. GET /sales/invoices/{id}/receipts.
sales_invoice_idrequiredPending sales orders
The ids of sales orders not yet delivered, optionally for one customer or a due-date range. GET /sales/orders/pending.
customer_iddue_date_todue_date_fromSales report
Invoiced sales totals grouped by day of week, day of month, month, year, salesman, customer, customer category, product, product category, county, state or branch, for a date range and optional filters. GET /reports/sales/invoices/{group}.
date_togroup_byrequiredbranch_iddate_fromproduct_idcustomer_idsalesman_idGet product stock
Stock of one product, optionally as of a date, in one warehouse or lot; with by_warehouse true, the stock in each warehouse. GET /production/products/{id}/stock or /stockByWarehouses.
lotdate_toproduct_idrequiredby_warehousewarehouse_idList stock of all products
Stock of every product, optionally as of a date, for one warehouse or one product category. Can be large: filter by warehouse or category. GET /production/products/stock.
date_towarehouse_idproduct_category_idProduct kardex
The stock movements (kardex) of one product, optionally to a date and for one warehouse. GET /production/products/{id}/kardex.
date_toproduct_idrequiredwarehouse_idBalance sheet
The balance sheet (balance general) as of a date, either the standard layout or the totals layout. GET /accounting/balanceSheet/standard or /totals.
layoutbook_iddate_toshow_levelscost_center_idshow_accounts_with_zero_balanceshow_only_accounts_with_activityProfit and loss
The profit and loss statement (estado de resultados) for a date range. GET /accounting/profitAndLoss.
book_iddate_todate_fromshow_levelscost_center_idshow_accounts_with_zero_balanceshow_only_accounts_with_activityGeneral ledger
The general ledger (libro mayor) movements of an account or a range of account numbers, for a date range. GET /accounting/ledger.
limitoffsetbook_iddate_todate_fromcost_center_idaccount_number_toaccount_number_fromrequiredPurchase ledger
The purchases ledger (libro de compras) for a year and month. GET /purchases/invoices/ledger.
yearmonthCreate a customer
WRITE: creates a new customer in Laudus (the customer id is assigned by Laudus; the customer record is not an invoice and sends nothing). Check laudus_list_customers for the RUT first to avoid duplicates. Laudus may require more fields than given and answers with its validation message. POST /sales/customers.
citynamerequiredemailnotesphonecountyvat_idaddressdte_emaillegal_nameactivity_name100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably realtime messaging: inspect channel history, presence and occupancy, publish messages, and review app usage and configuration.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant look up Woffu company users, employment contracts, departments and offices.
io.usefulapiOfficial publisher
Hosted MCP server for White Label Loyalty: browse rewards, read a customer's points wallet and tier progress, and buy rewards with points.
io.usefulapiOfficial publisher
Hosted Weekdone connector that lets an assistant read weekly reports, teams, objectives and KPIs, and add report items, comments and KPI values.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant list WebinarKit webinars, their dates, series, meetings and white-label sub-accounts.
{ "mcpServers": { "laudus": { "url": "https://laudus.usefulapi.io/mcp" } }}