Lightspeed Retail X-Series
Read and manage products, stock, sales, customers and pricing in your Lightspeed X-Series POS.
Connects to Lightspeed X-Series retail POS systems. Muse can read products, inventory levels, sales reports, customers and staff; search by date, outlet or payment type; update prices and stock counts; and create or edit customer records.
Try asking Muse: "Show me my total sales for this week broken down by payment type and top products."
See the most upvoted connectors
Source: Found in the official MCP Registry (io.usefulapi/lightspeed-x-series) · First listed October 29, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://lightspeed-x-series.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
Lightspeed Retail X-Series is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://lightspeed-x-series.usefulapi.io/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 207ms. Worked in n/a of checks over 30 days.
Screening · October 29, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 30
lightspeedxseries_get_retailerThe 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_list_outletsList 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_get_outletOne outlet by id. GET /outlets/{outlet_id}.lightspeedxseries_list_registersList registers (tills): id, name, outlet_id, is_open, open/close times and invoice numbering. Paginate with next_after. GET /registers.lightspeedxseries_get_register_payments_summaryPayment 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_list_taxesList 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_usersList 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_get_user_sale_totalsSales 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_productsList 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 (stolightspeedxseries_get_productOne product (variant) by id, with its prices, codes, suppliers and outlet taxes. GET /products/{product_id}.lightspeedxseries_search_productsFilter 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_get_inventory_levelsStock 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_lightspeedxseries_list_brandsList product brands (id, name). Paginate with next_after. GET /brands.lightspeedxseries_list_tagsList product tags (id, name). Paginate with next_after. GET /tags.lightspeedxseries_list_suppliersList suppliers: id, name, default markup and contact details. Paginate with next_after. GET /suppliers.lightspeedxseries_list_consignmentsList 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 wilightspeedxseries_get_consignmentOne consignment (stock order, transfer, stocktake or return) by id. GET /consignments/{consignment_id}.lightspeedxseries_list_consignment_productsThe 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_salesSales 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. Palightspeedxseries_get_saleOne sale by id with its line items, payments, taxes and totals. GET /sales/{sale_id}.lightspeedxseries_search_salesFind 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. lightspeedxseries_sales_summaryTotals 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.lightspeedxseries_list_customersList 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_search_customersFind 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_get_customerOne customer by id: contact details, addresses, customer group, balance, loyalty balance, year-to-date spend. GET /customers/{customer_id}.lightspeedxseries_list_customer_groupsList 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_create_customerWRITE: 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_update_customerWRITE: 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 plightspeedxseries_update_product_pricesWRITE: 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 nlightspeedxseries_set_product_stockWRITE: 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_inventoryLink
https://lightspeed-x-series.usefulapi.io/mcpQuestions about Lightspeed Retail X-Series in Muse
How do I connect Lightspeed Retail X-Series to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Lightspeed Retail X-Series to help me. It is a free service with an MCP server at https://lightspeed-x-series.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is Lightspeed Retail X-Series working right now?
At the last check (October 29, 2026, 21:26 UTC) the endpoint was working, answering in 207ms. It is checked every 15 minutes.
Is Lightspeed Retail X-Series safe to connect to Muse?
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can Lightspeed Retail X-Series do in Muse?
It exposes 30 tools, including lightspeedxseries_get_retailer, lightspeedxseries_list_outlets, lightspeedxseries_get_outlet, lightspeedxseries_list_registers. For example, you could ask Muse: "Show me my total sales for this week broken down by payment type and top products."
Follow Lightspeed Retail X-Series
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/lightspeed-x-series)). If you build Lightspeed Retail X-Series, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/lightspeed-retail-x-series"><img src="https://musedirectory.ai/badge/lightspeed-retail-x-series.svg" alt="Lightspeed Retail X-Series on musedirectory.ai" width="236" height="40"></a>