Lightspeed Retail (X-Series) MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Lightspeed Retail (X-Series) MCP by usefulapi is answering right now. Last checked 2 min ago. It exposes 30 tools. Last commit 25 Oct 2026.

Read Lightspeed X-Series products, stock, sales, customers, stock orders; one-call sales reports.

Uptime history 47 hours of history

47 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

290 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

and 5 more, back to 24 October 2026

Nothing serious here today

Today is the operative word: we check Lightspeed Retail (X-Series) MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add lightspeed-x-series --transport http https://lightspeed-x-series.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://lightspeed-x-series.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.lightspeed-x-series]
url = "https://lightspeed-x-series.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "lightspeed-x-series": {
      "url": "https://lightspeed-x-series.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "lightspeed-x-series": {
      "type": "http",
      "url": "https://lightspeed-x-series.usefulapi.io/mcp"
    }
  }
}

Available tools 30

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lightspeedxseries

lightspeedxseries_create_customer

WRITE: create a new customer. Give at least a first name, last name or company name. Check search_customers first so you do not create a duplicate. POST /customers.

lightspeedxseries_get_consignment

One consignment (stock order, transfer, stocktake or return) by id. GET /consignments/{consignment_id}.

lightspeedxseries_get_customer

One customer by id: contact details, addresses, customer group, balance, loyalty balance, year-to-date spend. GET /customers/{customer_id}.

lightspeedxseries_get_inventory_levels

Stock on hand per product per outlet: product_id, location_id (= outlet id), current_inventory_level, reorder threshold/amount, quantity_to_procure, average cost, total cost, supplier. Filter by outlet_ids, product_ids (or root_product_ids for variant families), supplier_ids; to_be_procured_only keeps products with a positive quantity_to_procure (the vendor's re-order suggestion, which accounts for open orders); for a plain below-reorder-point list, compare current_inventory_level with reorder_threshold yourself. Offset paging: pass next_offset to continue (null = last page). Read-only even though the vendor takes the filter as a POST body. POST /inventory_levels.

lightspeedxseries_get_outlet

One outlet by id. GET /outlets/{outlet_id}.

lightspeedxseries_get_product

One product (variant) by id, with its prices, codes, suppliers and outlet taxes. GET /products/{product_id}.

lightspeedxseries_get_register_payments_summary

Payment totals by payment type for one register since it was opened (the end-of-day / cash-up view). GET /registers/{register_id}/payments_summary.

lightspeedxseries_get_retailer

The connected store: id, name, domain prefix, store URL, country, currency, time zone, tax-exclusive setting, loyalty and gift-card settings. Good first call (use the time zone to turn a local day into UTC for sales searches). GET /retailer.

lightspeedxseries_get_sale

One sale by id with its line items, payments, taxes and totals. GET /sales/{sale_id}.

lightspeedxseries_get_user_sale_totals

Sales totals for one staff user, as the vendor computes them (no date filter; use sales_summary for a period). GET /users/{user_id}/sale_totals.

lightspeedxseries_list_brands

List product brands (id, name). Paginate with next_after. GET /brands.

lightspeedxseries_list_consignment_products

The product lines of one consignment: product_id, SKU, ordered count, received quantity, cost. Paginate with next_after (stop when data is empty). GET /consignments/{consignment_id}/products.

lightspeedxseries_list_consignments

List consignments: supplier stock orders (type SUPPLIER), transfers between outlets (OUTLET), stocktakes (STOCKTAKE) and returns (RETURN), with status (OPEN, SENT, DISPATCHED, RECEIVED, STOCKTAKE_*, CLOSED, CANCELLED), outlet, supplier, due and received dates, totals. Paginate with next_after. GET /consignments.

lightspeedxseries_list_customer_groups

List customer groups (id, name). Use the id as customer_group_id when creating or updating a customer. Paginate with next_after. GET /customer_groups.

lightspeedxseries_list_customers

List customers in version order: id, customer_code, name, email, phone, balance, loyalty_balance, year_to_date, customer group. To find one by name or email use search_customers. Paginate with next_after (stop when data is empty). GET /customers.

lightspeedxseries_list_outlets

List the store's outlets (locations): id, name, address, currency, time zone, default tax. Use the outlet id to filter sales, stock and stock orders. Paginate with next_after. GET /outlets.

lightspeedxseries_list_products

List products (variants) in the catalog: id, family_id, sku, variant_name, prices (price_excluding_tax / price_including_tax), active flags, codes, suppliers, version. The product NAME lives on the product family: add includes=["families"] to get it. Paginate with next_after (stop when data is empty). With sku set, only that SKU is looked up and the other filters are ignored. For text/brand/supplier filters use search_products; for stock use get_inventory_levels. GET /products.

lightspeedxseries_list_registers

List registers (tills): id, name, outlet_id, is_open, open/close times and invoice numbering. Paginate with next_after. GET /registers.

lightspeedxseries_list_sales

Sales in version order, oldest changes first: the way to sync everything that changed. It has NO date filter: for a period use search_sales or sales_summary. Each sale: id, date, invoice_number, state, customer_id, source (outlet, register, user), payments, line_items, totals. Paginate with next_after (stop when data is empty). GET /sales.

lightspeedxseries_list_suppliers

List suppliers: id, name, default markup and contact details. Paginate with next_after. GET /suppliers.

lightspeedxseries_list_tags

List product tags (id, name). Paginate with next_after. GET /tags.

lightspeedxseries_list_taxes

List tax groups and their rates (id, name, is_default, rates). The vendor returns the whole list in one reply (no cursor). GET /taxes.

lightspeedxseries_list_users

List the store's users (staff): id, username, display name, email, account type (cashier, manager, admin), enabled flag, restricted outlets. Paginate with next_after. GET /users.

lightspeedxseries_sales_summary

Totals for a period computed here from up to max_pages x page_size sales, so a report needs ONE tool call instead of dozens: sale count and net / tax / gross (tax-inclusive) totals, plus breakdowns by state, UTC day, outlet and payment type name, and the top products by quantity. By default only closed sales are counted (states containing 'closed'); set counted_states to change that. Dates are UTC (convert local days with the retailer's time zone). If the reply says truncated, call again with offset = next_offset and add the figures up. Uses GET /search?type=sales.

lightspeedxseries_search_customers

Find customers by email, first name, last name, company name, phone, mobile or customer code. Uses offset paging: pass next_offset to continue (null = last page). GET /search?type=customers.

lightspeedxseries_search_products

Filter products by SKU, brand, supplier, tag, product type or variant parent. Uses offset paging: pass next_offset to continue (null = last page). GET /search?type=products.

lightspeedxseries_search_sales

Find sales by date range (UTC), state, outlet, register, user, customer, payment type, product or invoice number. Uses offset paging: pass next_offset to continue (null = last page). Replies can be large: for totals over a period use sales_summary instead of paging through this. GET /search?type=sales.

lightspeedxseries_set_product_stock

WRITE: set the stock on hand (current_amount) and/or the reorder point and reorder amount of ONE product at ONE outlet. current_amount is the NEW TOTAL on hand, not a change: it overwrites the count, so sales made since you last read it are lost from the count. Read get_inventory_levels first and confirm the number with the user. Other outlets and all other product fields stay as they are. PATCH /products/{product_id} (outlet_inventories).

lightspeedxseries_update_customer

WRITE: change fields of an existing customer. Only the fields you pass change: the tool first reads the customer and sends the vendor its full record with your changes applied (the vendor's update is a full PUT). Cannot delete a customer or change balances. Lightspeed offers no partial update for customers, so a change made by someone else in the moments between the tool's read and its write can be overwritten. PUT /customers/{customer_id}.

lightspeedxseries_update_product_prices

WRITE: set the selling price of one product (variant). Pass price_excluding_tax or price_including_tax as a decimal string such as "24.99" (set one; the store's tax setting decides which the till uses). Nothing else on the product changes. Read the product first and confirm the new price with the user. PATCH /products/{product_id}.

Endpoints

URL	Transport	State	Latency	Checked
https://lightspeed-x-series.usefulapi.io/mcp	streamable-http	answering	142 ms	2 min ago

Alternatives to Lightspeed Retail (X-Series) MCP by usefulapi

same job, measured the same way

PHP Point of Sale MCP by usefulapi

by usefulapi

Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses.

26 tools answering

CashCtrl MCP by usefulapi

by usefulapi

Read CashCtrl accounts, journal, orders, people, articles, salaries and reports; book and create.

28 tools answering

Gumroad MCP by usefulapi

by usefulapi

Read products, sales, subscribers and offer codes; verify, enable and disable product licenses.

20 tools answering

Merit Aktiva MCP by usefulapi

by usefulapi

Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.

26 tools answering

Medusa

by trhonpavel

Medusa v2 store: orders, customers, products, inventory, sales reports and safe write actions.

32 installs/wk local only

Sendlane MCP by usefulapi

by usefulapi

Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.

31 tools answering

Shopware MCP

by bnymndev

Query and safely manage a Shopware 6 shop: products, orders, customers, stock, audits, reports.

31 installs/wk local only

Dukon AI — BILLZ store analytics

by dukonai

BILLZ (Billz) retail store analytics: revenue, profit, stock, top products, customers, reports

answering

Lightspeed Retail (X-Series) MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Lightspeed Retail (X-Series) MCP by usefulapi do?

It exposes 30 tools, read directly from the server on our last check. Among them: lightspeedxseries_create_customer, lightspeedxseries_get_consignment, lightspeedxseries_get_customer, lightspeedxseries_get_inventory_levels, lightspeedxseries_get_outlet, lightspeedxseries_get_product and 24 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Lightspeed Retail (X-Series) MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 290 ms. The bar chart above shows every period we have measured.

How do I connect Lightspeed Retail (X-Series) MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Lightspeed Retail (X-Series) MCP by usefulapi need an API key?

No. Lightspeed Retail (X-Series) MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 30 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Lightspeed Retail (X-Series) MCP by usefulapi?

It answers our handshake in 290 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Lightspeed Retail (X-Series) MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at lightspeed-x-series.usefulapi.io, which runs on its operator's own terms.