What Bridge actually does

Most retail "AI" tools want you to upload a spreadsheet, or they bolt a chat box onto a dashboard you already don't read. Bridge is different, and the difference is boring in the best way: it connects the AI assistant you already use to the data you already have.

The short version

Bridge is a hosted MCP server. Your AI assistant — Claude, or anything that speaks the Model Context Protocol — connects to it once, and from then on it can answer questions about your store using live Lightspeed data. Sales, inventory, customers, work orders, purchase orders, employee hours. Read access, structured, current.

You ask "how did the Encinitas shop do last weekend versus the same weekend last year?" and it answers from your actual numbers — not a guess, not a stale export.

Why we built it this way

• No export step. The data stays in sync on its own. You're never the integration.
• Read-only by default. Bridge can't change your books. It reads.
• Per-store isolation. Your data lives in its own database. Nothing is pooled with another retailer's.

That's it. No revolution, no platform to learn. It plugs into the workflow you've got and gets out of the way.

What's next

We'll use this space for the unglamorous stuff that actually helps: how to phrase a question so the assistant nails it, what we learned wiring up the Lightspeed API, and the occasional honest note about what Bridge can't do yet.

If you run a shop on Lightspeed and want to try it, start here.