mcpbeat Sign in

Laudus MCP by usefulapi MCP Server

answering

Laudus MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 38 tools. Last commit 1 Nov 2026.

Read Laudus ERP customers, sales, purchases, stock and accounting reports; create customers.

Uptime history 6 days of history · worst day 99%
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
38
Tools
read from the server
166 ms
Response time
average over 24h
1
Stars
last commit 1 Nov 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day
30 Oct a tool changed version2 times that day
29 Oct a tool changed version2 times that day
28 Oct a tool changed version
27 Oct a tool changed version
and 5 more, back to 27 October 2026

Laudus MCP by usefulapi missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add laudus --transport http https://laudus.usefulapi.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://laudus.usefulapi.io/mcp
~/.codex/config.toml
[mcp_servers.laudus]
url = "https://laudus.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "laudus": {
      "url": "https://laudus.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "laudus": {
      "type": "http",
      "url": "https://laudus.usefulapi.io/mcp"
    }
  }
}

Available tools 38

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

laudus
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_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_customer_credit_limit
A customer's credit limit and how much of it is used. GET /sales/customers/{id}/creditLimit.
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_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_get_customer
Get a customer (addresses, contact data, credit limit, category, salesman, price list) by id. GET /sales/customers/{id}.
laudus_get_journal_entry
Get an accounting journal entry (comprobante) with its lines by id. GET /accounting/journal/entries/{id}.
laudus_get_product
Get a product (SKU, description, category, units, prices) by id. GET /production/products/{id}.
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_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_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_supplier
Get a supplier by id. GET /purchases/suppliers/{id}.
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_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_list_customer_contacts
The contact people of a customer. GET /sales/customers/{id}/contacts.
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_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_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_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_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_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.
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_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_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_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_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_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_product_kardex
The stock movements (kardex) of one product, optionally to a date and for one warehouse. GET /production/products/{id}/kardex.
laudus_profit_and_loss
The profit and loss statement (estado de resultados) for a date range. GET /accounting/profitAndLoss.
laudus_purchase_ledger
The purchases ledger (libro de compras) for a year and month. GET /purchases/invoices/ledger.
laudus_sales_invoice_receipts
The customer payments (cobros) applied to one sales invoice. GET /sales/invoices/{id}/receipts.
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}.

Endpoints

URLTransportStateLatencyChecked
https://laudus.usefulapi.io/mcp streamable-http answering 155 ms 8 min ago

Alternatives to Laudus MCP by usefulapi

same job, measured the same way
PHP Point of Sale MCP by usefulapi
by usefulapi

Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses.

26 tools answering
CashCtrl MCP by usefulapi
by usefulapi

Read CashCtrl accounts, journal, orders, people, articles, salaries and reports; book and create.

28 tools answering
Lightspeed Retail (X-Series) MCP by usefulapi
by usefulapi

Read Lightspeed X-Series products, stock, sales, customers, stock orders; one-call sales reports.

30 tools answering
Merit Aktiva MCP by usefulapi
by usefulapi

Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.

26 tools answering
Lawcus MCP by usefulapi
by usefulapi

Read Lawcus contacts, matters, leads, time and billing reports; create contacts and tasks.

27 tools answering
KashFlow MCP by usefulapi
by usefulapi

Read KashFlow invoices, customers, suppliers, banking and reports; add customers, notes.

38 tools answering
MoeGo MCP by usefulapi
by usefulapi

Read customers, pets, appointments, orders and reports; add customer notes in MoeGo.

31 tools answering
Fitssey MCP by usefulapi
by usefulapi

Read Fitssey schedules, class capacity, stock, pass pricing, sales and attendance reports.

15 tools answering

Laudus MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Laudus MCP by usefulapi do?
It exposes 38 tools, read directly from the server on our last check. Among them: laudus_balance_sheet, laudus_create_customer, laudus_customer_credit_limit, laudus_customer_pending_invoices, laudus_general_ledger, laudus_get_customer and 32 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Laudus MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 166 ms. The bar chart above shows every period we have measured.
How do I connect Laudus MCP by usefulapi?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Laudus MCP by usefulapi need an API key?
No. Laudus MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 38 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Laudus MCP by usefulapi?
It answers our handshake in 166 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Laudus MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at laudus.usefulapi.io, which runs on its operator's own terms.