Laudus MCP by usefulapi

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Buchhaltung, Finanzen & Steuern

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

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

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• 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

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde über die Domain usefulapi.io bestätigt (die Registry prüft, wem die Domain gehört)

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 43 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 38 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Buchhaltung, Finanzen & Steuerni

• Mehr Sterne als 0 % der anderen 1721 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 97 % der anderen 1721 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 1721 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

{