Laudus MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 会计、财务与税务

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://laudus.usefulapi.io/mcp

claude mcp add --transport http laudus https://laudus.usefulapi.io/mcp

{
  "mcpServers": {
    "laudus": {
      "url": "https://laudus.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "laudus": {
      "type": "http",
      "url": "https://laudus.usefulapi.io/mcp"
    }
  }
}

https://laudus.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 43 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 38 个工具描述，未发现针对 AI 的隐藏指令

与“会计、财务与税务”中的其他服务器比较i

• 星标数多于此分类中其他 1720 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1720 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 1720 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{