What is MCP, and why does it matter for your shop?

Your AI assistant already knows your calendar, your email, and probably how you take your coffee. It does not know that the bike a customer ordered six weeks ago is still on backorder and they called yesterday asking about it.

That's the gap MCP closes. Let me explain it without the acronym soup.

MCP, in one breath

MCP stands for Model Context Protocol. Strip the jargon and it's this: a standard way for an AI assistant to talk to other software.

Think of it like the headphone jack. Before there was a standard plug, every pair of headphones needed its own special connector for every device. Once everyone agreed on one shape, any pair of headphones worked with anything. MCP is that agreed-on shape, but for AI assistants reaching out to your other tools.

Anthropic introduced it in late 2024. Through 2025, the other major assistants adopted it too. Today, when an assistant can "connect to" your files, your calendar, or some app, MCP is usually the thing making that possible behind the scenes. You don't have to think about it any more than you think about the headphone jack. You just plug in.

Why this matters for a Lightspeed shop

Here's the part that's actually about your store.

Your point-of-sale holds the answers to most of the questions you ask yourself in a week. What sold. What didn't. Who your best customers are. Which service jobs are still open. The data is all in Lightspeed Retail.

Your AI assistant is good at answering questions — but only about things it can reach. Out of the box, it can't reach your Lightspeed data. There's no plug for it. So you end up doing what you've always done: running a report, exporting it, maybe pasting it into a chat and hoping the assistant makes sense of a stale snapshot.

MCP is the plug. It's the piece that lets the assistant you already pay for actually talk to your store. With it, "which items haven't moved in ninety days at the Eastside shop?" becomes a question you type instead of a report you build.

What MCP is not

A few things it's easy to confuse it with:

• It's not a new chatbot to learn. You keep using the assistant you already use. MCP works underneath it.
• It's not a dashboard. No new charts, no new login, no screen to check. The answers come back in the conversation you're already having.
• It's not your POS vendor's built-in AI. POS companies are adding AI features to their own products, on their own schedule, inside their own walls. MCP flips that around: your assistant — the one you also use for email, drafting, planning — gets access to the store, and it can reason across all of it at once. You're not locked into one vendor's roadmap.

That last one is the real difference. A feature inside your POS can only ever see your POS. Your own assistant, connected through MCP, can take your sales numbers and cross them with the email you're writing to a vendor, or the calendar for next week's event. Same assistant, more reach.

Where Bridge comes in

MCP is the standard. Something still has to sit between your assistant and your Lightspeed account, speak that standard on one side and Lightspeed on the other, keep your data isolated and current, and not require you to be a developer to set it up.

That's Bridge. It's a hosted MCP server for Lightspeed Retail, built by Rizolvr. You connect it to your Lightspeed account once. From then on, your assistant can answer questions from your live data — read-only today, which means it reads your numbers and never changes them.

The test is simple. Once it's connected, you open your assistant and type something you'd normally run a report for:

"How did service revenue this month compare to last March?"

And it answers. From your actual numbers.

If that's the part of your week you'd most like to get back, here's what Bridge costs — or read what Bridge actually does for the short version.