Read and manage sales, purchases, inventory and accounting data from Laudus ERP
Connects to Laudus ERP to read customers, sales invoices and orders, purchase orders and invoices, product inventory, accounting journals and reports. Allows creating new customers. Supports filtering, sorting and detailed financial reporting for small businesses.
Try asking Muse: "Show me all unpaid invoices from my customers this month and their credit limits."
Source: Found in the official MCP Registry (io.usefulapi/laudus) · First listed October 30, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 1 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://laudus.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Laudus MCP is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://laudus.usefulapi.io/mcpResponse time at the last check: 62ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
laudus_list_customersList 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. Wlaudus_list_sales_invoicesList 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, claudus_list_sales_ordersList 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 fulllaudus_list_sales_quotesList 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 thelaudus_list_sales_receiptsList 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 =laudus_list_productsList 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, discontilaudus_list_product_categoriesList 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 /prodlaudus_list_warehousesList 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/wlaudus_list_salesmenList 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/laudus_list_suppliersList 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 = laudus_list_purchase_invoicesList 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 fulaudus_list_purchase_ordersList 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 ilaudus_list_accountsList 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 +laudus_list_journal_entriesList 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.credlaudus_list_cost_centersList 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 /laudus_get_customerGet a customer (addresses, contact data, credit limit, category, salesman, price list) by id. GET /sales/customers/{id}.laudus_get_sales_invoiceGet a sales invoice with its lines, taxes and totals by id. GET /sales/invoices/{id}.laudus_get_sales_orderGet a sales order with its lines by id. GET /sales/orders/{id}.laudus_get_sales_quoteGet a sales quote with its lines by id. GET /sales/quotes/{id}.laudus_get_productGet a product (SKU, description, category, units, prices) by id. GET /production/products/{id}.laudus_get_supplierGet a supplier by id. GET /purchases/suppliers/{id}.laudus_get_purchase_invoiceGet a purchase invoice with its lines by id. GET /purchases/invoices/{id}.laudus_get_purchase_orderGet a purchase order with its lines by id. GET /purchases/orders/{id}.laudus_get_journal_entryGet an accounting journal entry (comprobante) with its lines by id. GET /accounting/journal/entries/{id}.laudus_customer_pending_invoicesUnpaid 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.laudus_customer_credit_limitA customer's credit limit and how much of it is used. GET /sales/customers/{id}/creditLimit.laudus_list_customer_contactsThe contact people of a customer. GET /sales/customers/{id}/contacts.laudus_sales_invoice_receiptsThe customer payments (cobros) applied to one sales invoice. GET /sales/invoices/{id}/receipts.laudus_pending_sales_ordersThe ids of sales orders not yet delivered, optionally for one customer or a due-date range. GET /sales/orders/pending.laudus_sales_reportInvoiced 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}.laudus_get_product_stockStock 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.laudus_list_stockStock 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.laudus_product_kardexThe stock movements (kardex) of one product, optionally to a date and for one warehouse. GET /production/products/{id}/kardex.laudus_balance_sheetThe balance sheet (balance general) as of a date, either the standard layout or the totals layout. GET /accounting/balanceSheet/standard or /totals.laudus_profit_and_lossThe profit and loss statement (estado de resultados) for a date range. GET /accounting/profitAndLoss.laudus_general_ledgerThe general ledger (libro mayor) movements of an account or a range of account numbers, for a date range. GET /accounting/ledger.laudus_purchase_ledgerThe purchases ledger (libro de compras) for a year and month. GET /purchases/invoices/ledger.laudus_create_customerWRITE: 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 mhttps://laudus.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Laudus MCP to help me. It is a free service with an MCP server at https://laudus.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 30, 2026, 00:46 UTC) the endpoint was working, answering in 62ms. It is checked every 15 minutes.
It was screened on October 30, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 38 tools, including laudus_list_customers, laudus_list_sales_invoices, laudus_list_sales_orders, laudus_list_sales_quotes. For example, you could ask Muse: "Show me all unpaid invoices from my customers this month and their credit limits."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/laudus)). If you build Laudus MCP, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/laudus-mcp"><img src="https://musedirectory.ai/badge/laudus-mcp.svg" alt="Laudus MCP on musedirectory.ai" width="236" height="40"></a>