Claude + Lightspeed: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude connector for Lightspeed in Anthropic’s connectors directory, and Lightspeed doesn’t publish an MCP server. What Lightspeed does publish is a well-documented set of REST APIs — the Lightspeed Retail (X-Series) API for its retail POS and the Restaurant (K-Series) API for hospitality — plus the older Retail R-Series and eCom products. To get Claude talking to any of them you wrap that API in a custom MCP server yourself (a paid Claude plan is required to add custom connectors), or you use one of the unofficial community MCP servers that already do. Either way, it only runs inside a conversation you start — nothing watches your store between chats.
Here’s what actually exists across the Lightspeed products, how to wire it up, where the ceiling is, and what to use if you want Lightspeed-adjacent work that runs on its own.
What Claude can actually do with Lightspeed
Nothing out of the box — Claude has no built-in Lightspeed knowledge of your account. Everything depends on the API layer you connect it to. Be precise about which product you mean, because they’re separate platforms with separate APIs:
- Lightspeed Retail (X-Series) — the cloud retail POS (formerly Vend). Its API is JSON over HTTPS with read and write access to sales, products (including variants and composites), inventory (stock orders, counts, updates), customers, gift cards, pricebooks, promotions, and webhooks. It uses date-based versioning (e.g.
2026-01). - Lightspeed Restaurant (K-Series) — the hospitality POS. A separate REST API covering menus, orders, floor plans, and transactions.
- Lightspeed Retail (R-Series) and eCom — older/adjacent products with their own separate APIs.
Once you’ve stood up an MCP server over one of these, Claude can, inside a chat you’re driving:
- Answer questions grounded in live store data — “what were yesterday’s top sellers at the downtown location?” or “which products are below reorder point?” — if your server exposes those read endpoints.
- Draft and reason over the data — summarize a slow day, draft a reorder list, or explain a sales trend.
- Make changes if you let it — the X-Series API supports writes, so a server that exposes them could update a product price or create a stock order. Whether Claude can do that depends entirely on the scopes and endpoints you build in.
The community options confirm the pattern rather than replace it: there are unofficial Lightspeed MCP servers on GitHub and hosted third-party bridges (viaSocket, Zoho Flow) that wrap the X-Series API — none of them is from Anthropic or Lightspeed, and you’re trusting a third party with an API token.
How to set it up
There’s no toggle in Claude for this. The two honest paths:
- Build a custom MCP server over the Lightspeed API. Register an add-on (or generate a personal token) in your Lightspeed account, then authenticate with OAuth 2.0 — authorization code grant. Note the June 1, 2026 change: all new X-Series OAuth requests must include a
scopeparameter or they’re declined. Wrap the endpoints you need as MCP tools and add the server to Claude Desktop or Claude Code (custom connectors require a paid Claude plan). The K-Series API uses its own OAuth2 authorization-code flow. - Use a community/third-party MCP server. Faster, but it’s unofficial code and you’re handing a token to someone else’s bridge — vet it before pointing it at a live store.
Either way you’re doing developer work, and you’re maintaining it as Lightspeed versions its API.
The limits that matter
Even with a working server, the shape is “a smart analyst you prompt,” not “a system that runs your back office.” Four limits define it:
- No triggers. MCP tools only run inside a conversation you start. A sale, a stockout, a refund, an end-of-day close — none of it makes Claude do anything. The X-Series API has webhooks, but Claude can’t receive them; there’s no event listener on the Claude side. You have to be there, prompting.
- A local server, and a fixed-clock timer. A custom MCP server runs locally, so nothing happens while your machine is off. And Claude Cowork’s scheduled tasks fire on a fixed clock you set, not when a sale or a stockout happens — no good for a store that needs watching around the clock.
- Session-bound. Every action needs you in a live chat. There’s no standing watch on inventory or sales.
- Draft-only email. If you wanted Claude to email a supplier a reorder or send the owner a daily sales recap, note that Claude’s Gmail integration drafts but doesn’t send — the last step is still yours.
So Claude is genuinely useful for “pull this data and help me think about it” and simply isn’t built for “watch the store and act when something happens.”
If you want Lightspeed-adjacent work that runs on its own: Carly
The moment you want something to happen around Lightspeed without you in the chat — email a supplier when a product hits its reorder point, post a daily sales summary to Slack after close, flag a refund spike, sync a new customer into your CRM — you’ve crossed past what a chat-bound MCP server is for.
That’s where Carly fits. Lightspeed is a native Carly integration, and Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud. When inventory drops below a threshold or the day closes, Carly reacts — summarizes the numbers, emails the owner, updates a record, posts to Slack — while your laptop is closed.
- Actually reads and writes, and sends. Carly can pull sales and stock, update orders and inventory, manage tasks, update your CRM, record meetings, and it drafts and sends email across Gmail and Outlook — the follow-through that stops at the chat with Claude.
- Builds the workflow by interviewing you. Tell Carly “when a product drops below 5 units, draft a reorder email to the supplier and post it to our ops channel for approval” in plain English; it interviews you and builds it. No MCP server to maintain, no prompt engineering.
Carly connects to 200+ tools across 40+ categories natively, plus any other tool via your own API key — paste it on carlyassistant.com/integrations. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations.
Claude vs Carly
| Claude (Lightspeed via MCP) | Carly | |
|---|---|---|
| Answer questions on live store data | Yes (if you build/host the server) | Yes |
| Official, supported connector | No (custom or community MCP) | Yes (native integration) |
| Read sales / inventory | Via your MCP server | Yes |
| Update products / orders / stock | Only if you build the write tools | Yes |
| Acts on Lightspeed triggers / events | No (webhooks unreachable in chat) | Yes |
| Daily sales recap, on schedule | No | Yes |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Works while laptop is closed | No (local server) | Yes (cloud, 24/7) |
| Setup | Build/host an MCP server over the API | Describe it in plain English |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude over the Lightspeed API is a smart analyst you prompt in a chat. Carly is a teammate that acts on store events as they land.
Frequently Asked Questions
Does Claude work with Lightspeed?
Not officially. There’s no Claude connector for Lightspeed in Anthropic’s directory, and Lightspeed doesn’t ship an MCP server. You can connect Claude by wrapping the Lightspeed Retail (X-Series) API (or the Restaurant K-Series API) in a custom MCP server, or by using an unofficial community server — in both cases you’re the one supplying and maintaining the API access.
Which Lightspeed API do I use — there are several products?
It depends on your product. Retail (X-Series), the cloud retail POS formerly called Vend, uses the X-Series API. Restaurant (K-Series) uses a separate REST API. The older Retail R-Series and eCom have their own APIs again. They’re distinct platforms, so build against the one your business actually runs on.
Can Claude react to a Lightspeed sale or a low-stock event automatically?
No. MCP tools respond only inside a conversation you start, so nothing fires on a Lightspeed event. The X-Series API offers webhooks, but Claude has no way to receive them. For “when stock runs low, email the supplier” or “after close, send the owner a recap,” you need a trigger-based assistant like Carly, which integrates natively with Lightspeed and runs in the cloud around the clock.
How do I connect Claude to Lightspeed?
Generate a personal token or register an add-on in Lightspeed, authenticate over OAuth 2.0 authorization-code grant (from June 1, 2026 new X-Series OAuth requests must include a scope parameter), wrap the endpoints you need as an MCP server, and add it to Claude Desktop or Claude Code — custom connectors require a paid Claude plan. Or use a vetted community server that already wraps the API.
More: Claude connectors · Can Claude send emails · Claude + Shopify · Claude + Square · Claude vs Carly · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
