# Laudus MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Laudus MCP

Read and manage sales, purchases, inventory and accounting data from Laudus ERP

- Record: https://musedirectory.ai/connector/laudus-mcp
- Category: Finance & Bills
- Developer: usefulapi (https://usefulapi.io/laudus/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 62ms, checked 2026-10-30T00:46:41Z
- Endpoint: https://laudus.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-30T00:46:41Z)
- Source: Found in the official MCP Registry (io.usefulapi/laudus) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Flaudus

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.

Example request: "Show me all unpaid invoices from my customers this month and their credit limits."

How to connect: Not 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.

Tools:
- laudus_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. W
- laudus_list_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, c
- laudus_list_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
- laudus_list_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
- laudus_list_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 =
- laudus_list_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, disconti
- laudus_list_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 /prod
- laudus_list_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/w
- laudus_list_salesmen: 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/
- laudus_list_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 = 
- laudus_list_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 fu
- laudus_list_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 i
- laudus_list_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 +
- laudus_list_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.cred
- laudus_list_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 /
- laudus_get_customer: Get a customer (addresses, contact data, credit limit, category, salesman, price list) by id. GET /sales/customers/{id}.
- laudus_get_sales_invoice: Get a sales invoice with its lines, taxes and totals by id. GET /sales/invoices/{id}.
- laudus_get_sales_order: Get a sales order with its lines by id. GET /sales/orders/{id}.
- laudus_get_sales_quote: Get a sales quote with its lines by id. GET /sales/quotes/{id}.
- laudus_get_product: Get a product (SKU, description, category, units, prices) by id. GET /production/products/{id}.
- laudus_get_supplier: Get a supplier by id. GET /purchases/suppliers/{id}.
- laudus_get_purchase_invoice: Get a purchase invoice with its lines by id. GET /purchases/invoices/{id}.
- laudus_get_purchase_order: Get a purchase order with its lines by id. GET /purchases/orders/{id}.
- laudus_get_journal_entry: Get an accounting journal entry (comprobante) with its lines by id. GET /accounting/journal/entries/{id}.
- laudus_customer_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.
- laudus_customer_credit_limit: A customer's credit limit and how much of it is used. GET /sales/customers/{id}/creditLimit.
- laudus_list_customer_contacts: The contact people of a customer. GET /sales/customers/{id}/contacts.
- laudus_sales_invoice_receipts: The customer payments (cobros) applied to one sales invoice. GET /sales/invoices/{id}/receipts.
- laudus_pending_sales_orders: The ids of sales orders not yet delivered, optionally for one customer or a due-date range. GET /sales/orders/pending.
- laudus_sales_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}.
- laudus_get_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.
- laudus_list_stock: 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.
- laudus_product_kardex: The stock movements (kardex) of one product, optionally to a date and for one warehouse. GET /production/products/{id}/kardex.
- laudus_balance_sheet: The 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_loss: The profit and loss statement (estado de resultados) for a date range. GET /accounting/profitAndLoss.
- laudus_general_ledger: The general ledger (libro mayor) movements of an account or a range of account numbers, for a date range. GET /accounting/ledger.
- laudus_purchase_ledger: The purchases ledger (libro de compras) for a year and month. GET /purchases/invoices/ledger.
- laudus_create_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 m

Screening checks:
- MCP handshake: pass (Answered in 62ms)
- Domain against threat feeds (Cloudflare security DNS): pass (laudus.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (38 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)