Lightspeed X-Series MCP

About

Lightspeed Retail X-Series (formerly Vend) holds a store's whole day: every sale, every stock movement, every customer. This server puts that data in front of Claude or any other MCP client, so you can ask “How did each store do yesterday?” or “Where do we still have the large one in navy?” and get the number back. Dates are local store dates, converted to the UTC bounds the API wants, so day totals match Lightspeed's own reports.

It's read-only in code, not by setting. Lightspeed's personal tokens carry no scopes — a token that can read your sales can also void them — so every tool sends GET (plus two read-only POST searches), there are no write tools, and a test parses the source and fails the build if a write ever creeps in. The only dependency is the MCP SDK; it runs over stdio, and can be hosted for a team behind an authenticating proxy so nobody else ever sees the token.

Highlights

• 35 tools — sales, revenue summaries, products, inventory, transfers, purchase orders, customers, gift cards, promotions, price books
• Answers, not endpoints — sales_summary groups revenue by outlet, day, staff or product in one call
• Read-only by construction — no write tools, a deny-list on api_get, and a test that enforces it on every push
• Sized for a chat window — big variant families and price books come back summarised unless you ask for everything
• Polite to the API — reference data cached, 429 retried after Retry-After

# Claude Code — runs straight from GitHub with uvx
$ claude mcp add lightspeed \
$   -e LIGHTSPEED_DOMAIN_PREFIX=mystore \
$   -e LIGHTSPEED_TOKEN=your-token \
$   -- uvx --from git+https://github.com/davidboulay/lightspeed-xseries-mcp lightspeed-xseries-mcp