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スターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

作者のREADME

{