Loyverse MCP by usefulapi
io.usefulapi/loyverse · v1.11.1
Query Loyverse POS receipts, shifts, items, inventory and customers, and update stock and customers.
MCPremoteno credentialsFinanceE-commerce
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 21 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 21 tools · 17 read, 4 write (incl. delete/pay) · Finance, E-commerce
Test call loyverse_get_merchant: needs a key: HTTP 401 (987 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://loyverse.usefulapi.io/mcpTools
21 tools listed at last check
loyverse_get_merchantFetch the merchant account this token belongs to — business name, email, country and currency. A cheap way to confirm the token works. Loyverse: GET /merchant/.loyverse_list_storesList the merchant's stores (locations) with their addresses. Store ids are what the receipt, shift and inventory filters take. Loyverse: GET /stores.loyverse_list_employeesList employees, with the stores each can access and whether they are the owner. Loyverse: GET /employees.loyverse_list_receiptsList sales and refund receipts, newest first, with line items, payments, discounts and taxes. Filter by store, time range or receipt numbers — the core of any sales question. Loyverse: GET /receipts.loyverse_get_receiptFetch a single receipt by its receipt number (e.g. 2-1008), with line items, modifiers, discounts, taxes and payments. Loyverse: GET /receipts/{receipt_number}.loyverse_list_shiftsList cash-register shifts with their cash, gross/net sales, refunds, discounts, taxes, per-payment-type totals and pay-in/pay-out movements — the end-of-day view. Loyverse: GET /shifts.loyverse_list_itemsList catalog items with their variants (SKU, barcode, price, cost, per-store pricing), category, taxes and modifiers. Loyverse: GET /items.loyverse_get_itemFetch a single catalog item by id, with its variants. Loyverse: GET /items/{item_id}.loyverse_list_variantsList item variants — the sellable SKUs — optionally for given items or one SKU. Variant ids are what inventory levels are keyed on. Loyverse: GET /variants.loyverse_list_categoriesList item categories. Loyverse: GET /categories.loyverse_list_inventoryList current stock (`in_stock`) per variant per store. Filter by stores and/or variants — the answer to 'what is running low?'. Loyverse: GET /inventory.loyverse_list_customersList loyalty customers, newest first, with visits, total spent and points balance. Filter by email or ids. Loyverse: GET /customers.loyverse_get_customerFetch a single customer by id, with visits, total spent and points balance. Loyverse: GET /customers/{customer_id}.loyverse_list_payment_typesList the payment types (cash, card, integrated terminals…) and the stores where each is available. Receipt payments reference these ids. Loyverse: GET /payment_types.loyverse_list_discountsList configured discounts (fixed/variable percent or amount, discount-by-points) and where they apply. Loyverse: GET /discounts.loyverse_list_taxesList taxes with their rate, whether they are INCLUDED in or ADDED to the price, and the stores they apply in. Loyverse: GET /taxes.loyverse_list_suppliersList suppliers with their contact details. Loyverse: GET /suppliers/.loyverse_upsert_customerCreate a loyalty customer, or update one by passing its `id`. Loyverse does not document whether omitted fields survive an update, so on update fetch the customer first and send the full record. Loyverse: POST /customers.loyverse_upsert_categoryCreate an item category, or rename/recolor one by passing its `id`. Loyverse: POST /categories.loyverse_upsert_supplierCreate a supplier, or update one by passing its `id`. Loyverse does not document whether omitted fields survive an update, so on update send the full record. Loyverse: POST /suppliers/.loyverse_set_inventory_levelsSet the ABSOLUTE stock (`stock_after`) of one or more variants at given stores — e.g. after a stock count. This overwrites the current level rather than adding to it; read the current levels with loyverse_list_inventory first so they can be restored. Loyverse: POST /inventory.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/loyverse)