Lightspeed eCom add-on

The Lightspeed MCP server lets Claude read data from your Lightspeed eCom (C-Series) shop through the official REST API: products, variants, categories, brands, orders with their line items, customers and coupons. Ask "what did this customer order last month?" or "which variants of this product are out of stock?" and Claude fetches the answer from your shop.

It is an add-on for mcp-core, the self-hosted MCP server that you run in Docker on your own server. Your Lightspeed API key and secret stay in the .env file on that server. Claude Desktop or Claude Code connects to mcp-core, and mcp-core talks to Lightspeed.

Can the Lightspeed MCP server change anything in my shop?

No. It is read-only by design, and that is not a setting. The Lightspeed MCP server contains no code that writes to Lightspeed at all, so there is no mode to switch and nothing a misconfigured seat can turn on. Every request is a GET.

That makes it a low-risk first step for shop owners who want Claude on their sales data but are not ready to let an AI touch orders or prices. Other add-ons on mcp-core start read-only and can be switched to read-write; this one stays read-only permanently.

How does Claude query Lightspeed?

The Lightspeed MCP server exposes two tools instead of a long list of fixed functions:

• lightspeed_list_endpoints returns the endpoints Claude can query, each with a short description.
• lightspeed_get runs a GET on one of those endpoints, with optional query parameters.

The allowed endpoints are products, variants, categories, brands, orders, customers and coupons. Claude can also request a single record by id, such as one order, or the line items of one specific order. Anything outside that allowlist is refused with an error before a request leaves mcp-core.

The Lightspeed MCP server returns results in pages of up to 50 items. Claude uses the page parameter to walk through larger sets, so "all orders from this week" works as several calls rather than one oversized response.

What do you need to set up Lightspeed?

You need API credentials from your Lightspeed eCom back office, plus the API base URL for your region and the shop language. Add them to the .env of your mcp-core install:

LIGHTSPEED_BASE_URL=https://api.webshopapp.com
LIGHTSPEED_LANGUAGE=nl
LIGHTSPEED_API_KEY=your-api-key
LIGHTSPEED_API_SECRET=your-api-secret

Shops in the EU use https://api.webshopapp.com; US shops use https://api.shoplightspeed.com. Then run ./mcp-update.sh. The Lightspeed setup guide lists every variable. New to mcp-core? The install guide covers the first setup from download to running container. After purchase you also receive an email with the variables this tool needs.

Can one install read several Lightspeed shops?

Yes. Set LIGHTSPEED_CONNECTIONS to a JSON array with an id, base URL, language, key and secret per shop. Both tools then get a required store parameter, and Claude has to say which shop it means. That matters for merchants with a separate shop per country or brand, and for agencies that look after several Lightspeed clients from one Lightspeed MCP server.

Who uses the Lightspeed MCP server?

Lightspeed eCom merchants who want quick answers about orders, customers and catalogue without exporting spreadsheets. Customer service teams that look up an order while answering a mail. Agencies that support Lightspeed shops and want one place to check client data.

Run WooCommerce on another shop? The WooCommerce MCP server gives Claude the same kind of order and product access there, and adds optional write actions for order status, notes and stock.