Laudus MCP by usefulapi

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Contabilidad, finanzas e impuestos

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

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

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• 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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

• ✓ Superada

  El creador coincide con el repo

  El nombre en el registro se verificó con el dominio usefulapi.io (el registro comprueba quién es dueño del dominio)

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 43 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 38 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Contabilidad, finanzas e impuestosi

• Más estrellas que el 0% de los otros 1720 servidores de esta categoría
• Publicado en el registro más recientemente que el 97% de los otros 1720 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 100% de los otros 1720 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

{