Skip to main content
Glama
akshayadeodiaspark

luxare-retail-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DIASPARK_BASE_URLNoBase URL for the Diaspark API environmenthttps://diasparkdemo.rw.diasparkonline.com

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_customersA

Search the Diaspark customer list (terminal/terminal/list_customers_all). All fields are optional filters; leave a field out to not filter on it.

sales_history_reportA

Run the Diaspark sales receipt / item sales history report (pos/point_of_sale_report/sales_receipt_with_item_report). Dates use YYYY/MM/DD format. Use raw_overrides for any of the report's other criteria fields (str1-str60, all1-all30, multiselect1-30, dec1-10, list1-10, etc).

inventory_searchA

Run the Diaspark on-hand-by-style inventory report (inventory/inventory_report/on_hand_report_by_style). Friendly filter fields (sku, serial, brand, category, vendor, store, location, department, subcategory, group, group_code, classification, collection, designer, vendor_style, rmsa, upc) each do an exact-match filter when provided. Use raw_overrides for anything else (e.g. the all1-all30 'select all' toggle flags, date ranges, or multiselect fields) - see the report's column definitions for the full str#/all# field mapping.

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/akshayadeodiaspark/luxare-retail-mcp'

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