Lightspeed Retail X-Series
Read retailer configuration, products, customers, and sales from Lightspeed Retail X-Series across independently connected retailer accounts.
Verdict
Common use cases
- Pull customer purchase history during support calls
- Check product stock levels without opening POS
- Generate weekly sales summaries for team meetings
- Audit payment types configured across locations
- Answer 'do we carry this item' questions instantly
Integration
- Vendor
- Lightspeed Retail X-Series
- Category
- other
- Auth
- OAUTH2
- Tools
- 7
- Composio slug
lightspeed
Tools
- Get Customer
Retrieve one Lightspeed customer by their exact customer ID.
- Get Product
Retrieve one Lightspeed product by its exact product ID.
- Get Retailer
Return the connected Lightspeed Retail X-Series retailer's identity, account status, configuration, and subscription state.
- List Customers
Return one cursor-controlled page of customers from the connected Lightspeed retailer.
- List Payment Types
Return one cursor-controlled page of payment types configured for the connected Lightspeed retailer.
- List Products
Return one cursor-controlled page of products from the connected Lightspeed retailer for catalog discovery.
- List Sales
Return one cursor-controlled page of sales from the connected Lightspeed retailer; an empty page is a successful no-sales result.
Setup
Setup guide
- 11. Inside any Switchy Project, click the '+' icon in the sidebar and choose 'Connect MCP'. 2. Search for 'Lightspeed Retail X-Series' and click Connect. 3. You'll redirect to Lightspeed's OAuth consent screen—log in with an admin account that has full API access. 4. Grant read permissions for customers, products, sales, and payment types when prompted. 5. Lightspeed redirects you back to Switchy; the MCP appears in your Project's tool list with a green checkmark. 6. Test the connection by typing '@Lightspeed Retail X-Series list the first five products in our catalog' in the chat. 7. The AI should return product names and IDs—if it does, setup is complete. 8. To invoke tools in any message, @mention the MCP by name and describe what data you need; the AI picks the right tool automatically.
What teammates see: by default, memories from Lightspeed Retail X-Series are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Customer Purchase Lookup
@Lightspeed Retail X-Series find customer ID 84729 and show me their last three purchases with dates and totals.
Inventory Spot Check
@Lightspeed Retail X-Series list all products with 'running shoe' in the name and tell me which ones we currently carry.
Daily Sales Snapshot
@Lightspeed Retail X-Series show me all sales from today, group them by payment type, and calculate the total revenue.
Payment Method Audit
@Lightspeed Retail X-Series list all payment types we accept and flag any that are marked inactive or disabled.
Catalog Export Prep
@Lightspeed Retail X-Series pull the first 50 products with their IDs, names, and prices, then format it as a table.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Lightspeed Retail X-Series list all products in our catalog and show me which ones have inventory below 10 units
The MCP returned a paginated list of 50 products from your Lightspeed catalog. After filtering, 12 products currently show inventory below 10 units: 'Organic Cotton Tee (Navy)' has 3 units, 'Ceramic Mug Set' has 7 units, 'Leather Wallet (Brown)' has 2 units, and nine others. Each entry includes product ID, SKU, current stock level, and retail price. This represents the first page of results; additional pages may contain more low-stock items.
This example demonstrates the List Products tool combined with AI-driven filtering. The MCP returns raw catalog data in pages; the AI applies your inventory threshold logic. OAuth2 scope must include product read access. Lightspeed's API rate limits apply—frequent catalog scans may hit daily quotas for high-volume retailers.
@Lightspeed Retail X-Series pull today's sales and calculate total revenue by payment type
The MCP retrieved 34 sales completed today. Total revenue breaks down as follows: Credit Card $2,847.50 (18 transactions), Cash $1,205.00 (12 transactions), Gift Card $340.00 (3 transactions), Store Credit $78.50 (1 transaction). The List Sales tool returned transaction timestamps, amounts, and payment type IDs; the List Payment Types tool mapped IDs to human-readable names. This summary reflects completed sales only—pending or voided transactions are excluded.
This example pairs List Sales with List Payment Types to produce a financial summary. The MCP fetches raw transaction records; the AI aggregates and categorizes them. Requires OAuth2 scopes for both sales and payment-type read access. Sales data is eventually consistent—recent transactions may appear with a short delay depending on Lightspeed's sync timing.
@Lightspeed Retail X-Series look up customer ID 98234 and summarize their purchase history and account status
Customer ID 98234 is 'Jordan Martinez' (email: jordan.m@example.com, phone: 555-0142). Account status: Active, loyalty tier Gold, joined March 2023. The Get Customer tool returned profile details but does not include transaction history—Lightspeed's X-Series API separates customer identity from sales records. To view Jordan's purchases, you would need to query List Sales filtered by customer ID in a separate request.
This example shows the Get Customer tool's scope and a key limitation: customer profiles and sales history live in separate API endpoints. The MCP retrieves identity and account metadata but cannot fetch purchase records in the same call. This is an architectural constraint of Lightspeed's API, not the MCP. Plan multi-step workflows for full customer insights.
Use-case deep-dives
When this MCP works for weekly stock audits across stores
A 3-store apparel chain runs weekly inventory checks where the ops manager compares Lightspeed product counts against physical counts. This MCP is the right call if you're pulling product catalogs and sale histories to spot discrepancies in a shared Switchy workspace. The List Products and List Sales tools give you cursor-controlled access to the full dataset without hitting rate limits. The catch: if you need real-time stock levels or warehouse transfer data, Lightspeed's API doesn't expose those through this MCP—you'll see products and completed sales, but not live inventory positions. This setup wins when your reconciliation is backward-looking (last week's sales versus current counts) rather than live. If your team reviews inventory weekly and can work from sales history, connect this MCP and build a shared audit prompt in Switchy.
This MCP handles small-scale customer segmentation well
A boutique coffee roaster with 800 regulars wants to identify high-value customers for a VIP tasting event. The marketing lead uses List Customers to pull the full roster, then filters by purchase frequency using List Sales cross-referenced to customer IDs. This MCP works because the dataset is small enough to paginate through in a single session, and OAuth2 keeps the connection secure across team members in Switchy. The boundary: if your customer base exceeds 10,000 or you need real-time purchase triggers, pagination becomes tedious and the MCP lacks webhook support for live events. This is a monthly or quarterly analysis tool, not a daily dashboard. If you're running infrequent segmentation on a few thousand customers and your team collaborates on the criteria in Switchy, this MCP delivers without needing a full BI stack.
When this MCP clarifies transaction trends for finance teams
A 2-person finance team at a garden center reviews payment mix every month to negotiate processor fees. They use List Payment Types to see configured methods, then cross-check List Sales to count transactions by type. This MCP is ideal because it exposes the exact payment breakdown Lightspeed tracks, and the 7-tool scope keeps the interface simple for non-technical users. The trade-off: you can't drill into refund reasons or chargeback details—those live outside the X-Series API surface. If your goal is a monthly summary of credit-versus-cash trends to inform vendor negotiations, this MCP gives you the raw counts without needing a data analyst. Connect it in Switchy, save a prompt template for the monthly pull, and your finance lead runs the report in under five minutes.
Frequently asked
What does the Lightspeed Retail X-Series MCP do in Switchy?
It connects your Lightspeed X-Series point-of-sale to Switchy so your AI agents can read customer records, product catalogs, sales transactions, and payment types. Your team can ask questions like "show me yesterday's sales" or "find this customer's order history" without opening the Lightspeed dashboard. It doesn't write data back—agents retrieve information only.
Do I need admin access to connect Lightspeed X-Series?
Yes. The OAuth2 flow requires a Lightspeed account with API access permissions, which typically means owner or admin level. During setup you'll authorize Switchy to read your retailer profile, customers, products, sales, and payment configurations. Standard staff accounts without API privileges can't complete the connection.
Can the MCP create or update products and sales in Lightspeed?
No. The seven tools are read-only—agents can retrieve customers, products, sales, and payment types but cannot modify inventory, process refunds, or change customer details. If your team needs to update records, they still use the Lightspeed dashboard or native app. This design prevents accidental data corruption from AI hallucinations.
How does this compare to exporting CSV reports from Lightspeed?
The MCP pulls live data on demand instead of requiring manual exports. Your agents query the current state of your catalog or sales without waiting for overnight batch jobs or downloading spreadsheets. You lose the ability to manipulate data offline, but you gain real-time answers and eliminate the export-import-analyze cycle for routine questions.
Who on the team should connect the Lightspeed integration?
Your store manager or whoever holds the Lightspeed admin credentials. Once connected, any Switchy workspace member can ask agents to query the data—they don't need separate Lightspeed logins. The connection counts as one integration slot in your Switchy plan, regardless of how many team members use it.