Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOYVERSE_ACCESS_TOKENYesYour Loyverse personal access token. Obtain it from Loyverse Back Office: Settings > Access Tokens.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
loyverse_get_merchantA

Get the Loyverse merchant (GET /merchant). Singleton resource: the merchant account itself. No id required. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_storeB

List stores from Loyverse (GET /stores). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_storeA

Get a single store by id (GET /stores/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_categoryA

List categories from Loyverse (GET /categories). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_categoryA

Get a single category by id (GET /categories/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_categoryB

Create a new category in Loyverse (POST /categories). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_categoryA

Update an existing category (POST /categories with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_categoryA

Delete a category by id (DELETE /categories/{id}). This is destructive and cannot be undone.

loyverse_list_itemA

List items from Loyverse (GET /items). Supports cursor pagination. Items contain nested variants. Variant stock is managed via the inventory resource. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_itemA

Get a single item by id (GET /items/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_itemA

Create a new item in Loyverse (POST /items). Items contain nested variants. Variant stock is managed via the inventory resource. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_itemA

Update an existing item (POST /items with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_itemA

Delete a item by id (DELETE /items/{id}). This is destructive and cannot be undone.

loyverse_list_modifierA

List modifiers from Loyverse (GET /modifiers). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_modifierA

Get a single modifier by id (GET /modifiers/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_modifierA

Create a new modifier in Loyverse (POST /modifiers). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_modifierA

Update an existing modifier (POST /modifiers with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_modifierA

Delete a modifier by id (DELETE /modifiers/{id}). This is destructive and cannot be undone.

loyverse_list_discountA

List discounts from Loyverse (GET /discounts). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_discountA

Get a single discount by id (GET /discounts/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_discountA

Create a new discount in Loyverse (POST /discounts). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_discountA

Update an existing discount (POST /discounts with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_discountA

Delete a discount by id (DELETE /discounts/{id}). This is destructive and cannot be undone.

loyverse_list_taxA

List taxes from Loyverse (GET /taxes). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_taxA

Get a single tax by id (GET /taxes/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_taxB

Create a new tax in Loyverse (POST /taxes). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_taxA

Update an existing tax (POST /taxes with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_taxA

Delete a tax by id (DELETE /taxes/{id}). This is destructive and cannot be undone.

loyverse_list_customerA

List customers from Loyverse (GET /customers). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_customerA

Get a single customer by id (GET /customers/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_customerA

Create a new customer in Loyverse (POST /customers). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_customerA

Update an existing customer (POST /customers with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_customerA

Delete a customer by id (DELETE /customers/{id}). This is destructive and cannot be undone.

loyverse_list_employeeA

List employees from Loyverse (GET /employees). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_employeeA

Get a single employee by id (GET /employees/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_pos_deviceA

List pos_devices from Loyverse (GET /pos_devices). Supports cursor pagination. Physical/virtual POS terminals, one per store. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_pos_deviceA

Get a single pos_device by id (GET /pos_devices/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_supplierA

List suppliers from Loyverse (GET /suppliers). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_supplierA

Get a single supplier by id (GET /suppliers/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_supplierA

Create a new supplier in Loyverse (POST /suppliers). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_supplierA

Update an existing supplier (POST /suppliers with "id" set — Loyverse uses the same create endpoint for updates when "id" is present in the body). This is not a partial patch: include all required fields for this resource, not just the ones changing, or Loyverse will reject the request. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_supplierA

Delete a supplier by id (DELETE /suppliers/{id}). This is destructive and cannot be undone.

loyverse_list_inventoryC

List inventory from Loyverse (GET /inventory). Supports cursor pagination. List returns stock levels per variant/store. Update expects a body like { inventory_levels: [{ variant_id, store_id, stock_after }] }. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_update_inventoryA

Update inventory stock levels (POST /inventory). List returns stock levels per variant/store. Update expects a body like { inventory_levels: [{ variant_id, store_id, stock_after }] }. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_shiftA

List shifts from Loyverse (GET /shifts). Supports cursor pagination. POS cash register shifts (corte de caja): opened_at/closed_at, starting_cash, cash_payments, expected_cash vs actual_cash, gross/net sales, cash_movements. Not in the official docs registry but verified live (200 on both list and get). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_shiftA

Get a single shift by id (GET /shifts/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_receiptA

List receipts from Loyverse (GET /receipts). Supports cursor pagination. Receipts cannot be updated or deleted through the API, only created and read. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_receiptA

Get a single receipt by id (GET /receipts/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_receiptA

Create a new receipt in Loyverse (POST /receipts). Receipts cannot be updated or deleted through the API, only created and read. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_payment_typeA

List payment_types from Loyverse (GET /payment_types). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_get_payment_typeA

Get a single payment_type by id (GET /payment_types/{id}). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_list_webhookA

List webhooks from Loyverse (GET /webhooks). Supports cursor pagination. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_create_webhookA

Create a new webhook in Loyverse (POST /webhooks). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

loyverse_delete_webhookA

Delete a webhook by id (DELETE /webhooks/{id}). This is destructive and cannot be undone.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ogarciabrena/mcploy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server