List your agent

Lightspeed Retail (X-Series) MCP by usefulapi

MCP server · hosted · v1.0.0 · io.usefulapi/lightspeed-x-series
Online · tested 1h agoNEW · 1h agoSeen in the registry 54m ago

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

Website ↗Source code ↗How to connect ↓

What it does

Lightspeed Retail (X-Series) MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: report generation. That makes it a candidate for tasks such as generate reports or analyze campaign performance.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen23 Oct 2026
Last checked54m ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

  • https://lightspeed-x-series.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http lightspeed-retail-x-series-mcp-by-usefulapi https://lightspeed-x-series.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE Lightspeed Retail (X-Series) MCP by usefulapi answered an MCP connection on 23 Oct 2026 and introduced itself as lightspeed-x-series-mcp 1.0.0 (MCP protocol 2025-06-18).

30 tools offered to AI assistants

  • 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_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_get_outlet · One outlet by id. GET /outlets/{outlet_id}.
  • 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_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_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_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_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"]
  • lightspeedxseries_get_product · One product (variant) by id, with its prices, codes, suppliers and outlet taxes. GET /products/{product_id}.
  • 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_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
Show 18 more
  • lightspeedxseries_list_brands · List product brands (id, name). Paginate with next_after. GET /brands.
  • lightspeedxseries_list_tags · List product tags (id, name). Paginate with next_after. GET /tags.
  • lightspeedxseries_list_suppliers · List suppliers: id, name, default markup and contact details. Paginate with next_after. GET /suppliers.
  • 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
  • lightspeedxseries_get_consignment · One consignment (stock order, transfer, stocktake or return) by id. GET /consignments/{consignment_id}.
  • 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_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,
  • lightspeedxseries_get_sale · One sale by id with its line items, payments, taxes and totals. GET /sales/{sale_id}.
  • 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_
  • 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
  • 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 /cust
  • 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_get_customer · One customer by id: contact details, addresses, customer group, balance, loyalty balance, year-to-date spend. GET /customers/{customer_id}.
  • 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_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_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
  • 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.
  • 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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers
Generate reports
Report Generation
50%
Analyze campaign performance
Report Generation
50%
Build dashboards
Report Generation
50%
Monitor company cash flow
Report Generation
50%
Analyze real estate
Report Generation
33%
Audit website SEO
Report Generation
33%
Build a literature review
Report Generation
33%
Create presentations
Report Generation
33%

Similar tools

Listed for the same task: generate reports
  • QueryActionREMOTELOCAL
    Site growth from your agent: GA4, Search Console, PageSpeed, SEO research and weekly reports
  • clariBIREMOTELOCAL
    AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client
  • Google Analytics 4REMOTELOCAL
    Google Analytics 4 MCP server: 27 read tools, no write tools
  • AdLoopREMOTELOCAL
    Google Ads, GA4 and Tag Manager in your AI client, with a preview before every change
  • Stats CompassREMOTELOCAL
    50+ pandas-powered tools for data loading, cleaning, visualization, and ML workflows
  • Pirsch Analytics MCP by usefulapiREMOTELOCAL
    Read Pirsch web analytics: visitors, pages, referrers, UTM, events, funnels and sessions

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://lightspeed-x-series.usefulapi.io/mcpDECLAREDSRC-001 Official MCP Registry54m ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry54m ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry54m ago
Websitehttps://usefulapi.io/lightspeed-x-series/DECLAREDSRC-001 Official MCP Registry54m ago
Repositoryhttps://github.com/m190/usefulapi-mcpDECLAREDSRC-001 Official MCP Registry54m ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry54m ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry54m ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry54m ago

Change history

  • NEW23 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Questions about Lightspeed Retail (X-Series) MCP by usefulapi

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

Use the hosted endpoint https://lightspeed-x-series.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Lightspeed Retail (X-Series) MCP by usefulapi offer?

When Electra Index connected on 23 Oct 2026, it listed 30 tools: lightspeedxseries_get_retailer, lightspeedxseries_list_outlets, lightspeedxseries_get_outlet, lightspeedxseries_list_registers, lightspeedxseries_get_register_payments_summary, lightspeedxseries_list_taxes, lightspeedxseries_list_users, lightspeedxseries_get_user_sale_totals and more. The full list is in "Live check" above.

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

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.

What can I use Lightspeed Retail (X-Series) MCP by usefulapi for?

Based on its description, it is most relevant to: generate reports, analyze campaign performance, build dashboards, monitor company cash flow.