UPOS Cloud POS MCP by usefulapi

Read customers, loyalty, menu, tax and sales reports; create or update customers in UPOS Cloud POS.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
90%
Naming quality
76%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'uposcloudpos_get_customer_loyalties' name length outside 3-30 rangein uposcloudpos_get_customer_loyalties
  • LOWTool 'uposcloudpos_transaction_report' name length outside 3-30 rangein uposcloudpos_transaction_report

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,883Tokens (tool definitions)
~1.3 KBTypical response size
Moderate attention impact (1.47% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "upos-cloud-pos": {
      "url": "https://upos-cloud-pos.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://upos-cloud-pos.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (11)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢uposcloudpos_list_customers

List the customers saved on the account (loyalty and contact records). UPOS API: GET /customers.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_get_customer(customer_id)

Get one customer record by customer id. UPOS API: GET /customer/{customer-id}.

Input Schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "The customer id."
    }
  },
  "required": [
    "customer_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_get_customer_loyalties(customer_id)

Get the loyalty balances and programs of one customer. UPOS API: GET /customer/{customer-id}/getCustomerLoyalties.

Input Schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "The customer id."
    }
  },
  "required": [
    "customer_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴uposcloudpos_create_customer(first_name, last_name, email, notes, membership_plan_id)

WRITE: create a customer record on the account. Only the fields you pass are sent. UPOS API: POST /customer.

Input Schema

{
  "type": "object",
  "properties": {
    "first_name": {
      "description": "Customer's first name.",
      "type": "string",
      "maxLength": 100
    },
    "last_name": {
      "description": "Customer's last name.",
      "type": "string",
      "maxLength": 100
    },
    "email": {
      "description": "Customer's e-mail.",
      "type": "string",
      "maxLength": 254
    },
    "notes": {
      "description": "Notes about the customer.",
      "type": "string",
      "maxLength": 2000
    },
    "membership_plan_id": {
      "description": "Membership plan id (Membership tab in the back office).",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡uposcloudpos_update_customer(customer_id, first_name, last_name, email, notes, ...)

WRITE: update one customer record. Only the fields you pass are sent. UPOS API: PUT /customer/{customer-id}.

Input Schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "The customer id."
    },
    "first_name": {
      "description": "Customer's first name.",
      "type": "string",
      "maxLength": 100
    },
    "last_name": {
      "description": "Customer's last name.",
      "type": "string",
      "maxLength": 100
    },
    "email": {
      "description": "Customer's e-mail.",
      "type": "string",
      "maxLength": 254
    },
    "notes": {
      "description": "Notes about the customer.",
      "type": "string",
      "maxLength": 2000
    },
    "membership_plan_id": {
      "description": "Membership plan id (Membership tab in the back office).",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    }
  },
  "required": [
    "customer_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_list_store_users(store_id)

List the users (staff) of one store. UPOS API: GET /store/{store-id}/users.

Input Schema

{
  "type": "object",
  "properties": {
    "store_id": {
      "description": "Store id. Omit to use the store set for this connection.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_get_user(user_id)

Get one user (staff member) by user id. UPOS API: GET /user/{user-id}.

Input Schema

{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$",
      "description": "The user id."
    }
  },
  "required": [
    "user_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_list_taxes(store_id)

List the taxes of one store. UPOS API: GET /store/{store-id}/taxes.

Input Schema

{
  "type": "object",
  "properties": {
    "store_id": {
      "description": "Store id. Omit to use the store set for this connection.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_list_menu_items(store_id)

List the menu items of one store (items sold on the POS). UPOS API: GET /store/{store-id}/menuItems.

Input Schema

{
  "type": "object",
  "properties": {
    "store_id": {
      "description": "Store id. Omit to use the store set for this connection.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_sale_report(store_id, date_option, number_of_days, specific_date, from_date, ...)

Read the department and category sale report of one store for a date range. UPOS API: GET /store/{store-id}/saleReport.

Input Schema

{
  "type": "object",
  "properties": {
    "store_id": {
      "description": "Store id. Omit to use the store set for this connection.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    },
    "date_option": {
      "type": "string",
      "enum": [
        "T",
        "Y",
        "LND",
        "W",
        "L7D",
        "M",
        "LM",
        "L30D",
        "SD",
        "DR"
      ],
      "description": "Date range: T today, Y yesterday, LND last N days (needs number_of_days), W this week, L7D last 7 days, M this month, LM last month, L30D last 30 days, SD one specific date (needs specific_date), DR date range (needs from_date and to_date)."
    },
    "number_of_days": {
      "description": "Days back, for date option LND.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 365
    },
    "specific_date": {
      "description": "Date for date option SD, format dd-Mon-yyyy (for example 29-Sep-2019).",
      "type": "string"
    },
    "from_date": {
      "description": "Start date for date option DR, format dd-Mon-yyyy.",
      "type": "string"
    },
    "to_date": {
      "description": "End date for date option DR, format dd-Mon-yyyy.",
      "type": "string"
    }
  },
  "required": [
    "date_option"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢uposcloudpos_transaction_report(store_id, date_option, number_of_days, specific_date, from_date, ...)

Read the transactions report (payments and tenders) of one store for a date range. UPOS API: GET /store/{store-id}/transactionReport.

Input Schema

{
  "type": "object",
  "properties": {
    "store_id": {
      "description": "Store id. Omit to use the store set for this connection.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,64}$"
    },
    "date_option": {
      "type": "string",
      "enum": [
        "T",
        "Y",
        "LND",
        "W",
        "L7D",
        "M",
        "LM",
        "L30D",
        "SD",
        "DR"
      ],
      "description": "Date range: T today, Y yesterday, LND last N days (needs number_of_days), W this week, L7D last 7 days, M this month, LM last month, L30D last 30 days, SD one specific date (needs specific_date), DR date range (needs from_date and to_date)."
    },
    "number_of_days": {
      "description": "Days back, for date option LND.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 365
    },
    "specific_date": {
      "description": "Date for date option SD, format dd-Mon-yyyy (for example 29-Sep-2019).",
      "type": "string"
    },
    "from_date": {
      "description": "Start date for date option DR, format dd-Mon-yyyy.",
      "type": "string"
    },
    "to_date": {
      "description": "End date for date option DR, format dd-Mon-yyyy.",
      "type": "string"
    }
  },
  "required": [
    "date_option"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded11 tools