mcp-loyverse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log verbosity: debug, info, warn, error | info |
| MCP_READ_ONLY | No | Read-only mode (always true in v0.1) | true |
| DEFAULT_TIMEZONE | No | Timezone for date presets (e.g. America/Mexico_City) | UTC |
| LOYVERSE_BASE_URL | No | API base URL | https://api.loyverse.com/v1.0 |
| LOYVERSE_API_TOKEN | Yes | Loyverse Personal Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthcheckB | Check server status and configuration |
| list_receiptsA | Search receipts (tickets) by date range, store, or receipt numbers. Returns receipt summaries with totals, line items, and payment info. Use date presets (today, yesterday, this_week, this_month) or explicit from/to range. |
| get_receiptB | Get full details of a specific receipt by its receipt number |
| list_itemsA | List items from the catalog. Useful to look up item names, prices, SKUs, and categories. |
| get_itemB | Get full details of a specific item by its ID |
| list_employeesA | List employees (waiters, cashiers, staff). Use to resolve employee names from IDs found in receipts. |
| get_employeeC | Get full details of a specific employee by their ID |
| list_customersA | List customers. Filter by IDs or email. Returns customer profiles with visit history and spending totals. |
| get_customerB | Get full details of a specific customer by their ID |
| list_storesB | List all stores. The stores endpoint does not support pagination — all stores are returned at once. |
| get_storeB | Get full details of a specific store by its ID |
| get_merchantA | Get merchant profile including business name and currency settings (code and decimal places) |
| sales_summaryA | Get a sales summary for a given period: total revenue, receipt count, average ticket, discounts, taxes, and tips. Use presets (today, yesterday, this_week, this_month) or explicit date range. |
| top_selling_itemsA | Get the top-selling items for a period, ranked by quantity sold or by sales amount. Answers: What was the best-selling dish today? |
| top_employees_by_salesA | Get the top employees (waiters/cashiers) by sales amount or receipt count. Answers: Which waiter sold the most this month? |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each core entity (employees, receipts, items, customers, stores) has a clearly distinct list vs. get pair. Analytics tools such as sales_summary, top_selling_items, and top_employees_by_sales target different questions and do not overlap with the catalog or receipt lookup tools.
The set predominantly follows a consistent snake_case verb_noun convention, e.g. list_employees, get_receipt, top_selling_items. The main deviation is healthcheck, which would be more consistent as health_check, but it is a minor and readable exception.
With 15 tools, the server is comfortably scoped for a POS data and reporting integration. Each major entity gets list/get coverage, while analytics and healthcheck add clear value without bloating the surface.
The tool set covers list/get access for employees, receipts, items, customers, stores, and merchant profile, plus useful sales and ranking analytics. It lacks create/update/delete operations, but for a read-only reporting MCP server the surface is nearly complete.