Laudus MCP by usefulapi
Read Laudus ERP customers, sales, purchases, stock and accounting reports; create…
- Runs
- Remotely
- Version
- 1.16.0
- Listing updated
- 4 days ago
About Laudus MCP by usefulapi
Laudus MCP by usefulapi is an MCP server for finance and payments. It runs as a hosted remote server, so there is nothing to install locally.
Read Laudus ERP customers, sales, purchases, stock and accounting reports; create customers.
Install
Run in a terminal
claude mcp add --transport http laudus https://laudus.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://laudus.usefulapi.io/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"laudus": {
"url": "https://laudus.usefulapi.io/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"laudus": {
"type": "http",
"url": "https://laudus.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"laudus": {
"serverUrl": "https://laudus.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"laudus": {
"type": "http",
"url": "https://laudus.usefulapi.io/mcp"
}
}
}Tools this server provides (38)
Read directly from the server.
- 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. When a page is full, ask for the next one with offset = offset + limit. POST /sales/customers/list.
- 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, customer.name, customer.VATId, totals.net, totals.total, items.product.sku, items.quantity. When a page is full, ask for
- 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, ask for the next one with offset = offset + limit. POST /sales/orders/list.
- 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 next one with offset = offset + limit. POST /sales/quotes/list.
- 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 = offset + limit. POST /sales/receipts/list.
- 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, discontinued. When a page is full, ask for the next one with offset = offset + limit. POST /production/products/list.
- 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 /production/products/categories/list.
- 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/warehouses/list.
- 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/list.
- 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 = offset + limit. POST /purchases/suppliers/list.
- 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 full, ask for the next one with offset = offset + limit. POST /purchases/invoices/list.
- 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 is full, ask for the next one with offset = offset + limit. POST /purchases/orders/list.
- 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 + limit. POST /accounting/accounts/list.
- 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.credit. When a page is full, ask for the next one with offset = offset + limit. POST /accounting/journal/entries/list.
- 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 /purchases/costcenters/list.
- 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 message. POST /sales/customers.
Laudus MCP by usefulapi FAQ
How do I add Laudus MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http laudus https://laudus.usefulapi.io/mcp
What are the best alternatives to Laudus MCP by usefulapi?
The closest alternatives to Laudus MCP by usefulapi are Solana MCP by Vybe, Tapetide - Indian Stock Market MCP, Budget Tracker, Quantivex Research and Provyan.
Alternatives to Laudus MCP by usefulapi

Solana MCP by Vybe
MCP serverRemote MCP server exposing the Vybe Solana API to AI clients and code editors
- 44 tools
- Remote
- 2.8K GitHub stars
- Finance and payments

Tapetide - Indian Stock Market MCP
MCP serverIndian NSE and BSE stock market data for AI assistants through 48 MCP tools
- 17 tools
- Remote
- Freemium
- 150 GitHub stars
- Finance and payments
Budget Tracker
MCP serverLocal MCP expense ledger that logs receipts and mileage, splits VAT and prepares rebilling
- 14 tools
- Remote
- Freemium
- 2 GitHub stars
- Finance and payments

Quantivex Research
MCP serverStock scores, what a price assumes, earnings quality and quiet profit revisions
- 11 tools
- Remote
- Free
- Finance and payments

Provyan
MCP serverBacktested crypto signal results on 94 coins, with luck odds and sources
- 4 tools
- Remote
- Free
- Finance and payments
TribuJus
MCP serverRead-only access to UK bank accounts, cards and transactions via TrueLayer Open Banking
Not checked yet- 5 tools
- Remote
- Open source
- Legal and government