Bridge by Rizolvr — Documentation

Bridge is a hosted Model Context Protocol (MCP) connector that gives a retailer's AI assistant secure access to their Lightspeed Retail (R-Series) point-of-sale data. Your assistant can ask plain-language questions about your business — top sellers, overdue work orders, dead stock, customers due for a visit — and get real answers grounded in your own POS data. On the Pro tier it can also make changes: prices, reorder points, tags, purchase orders, work orders.

Bridge is a flat monthly subscription, priced per shop location across three tiers — Standard, Premium, and Pro (the write tier) — with optional per-seat add-ons and roughly 50% off each additional shop. See the pricing page for current tiers and prices. Bridge is operated by Rizolvr LLC (Wyoming, USA), hosted with Amazon Web Services in the United States.

1. Sign up at portal.rizolvr.com. Pick a tier and complete payment.
2. Connect your Lightspeed Retail (R-Series) account by clicking the "Connect Lightspeed" button. You'll be redirected to Lightspeed to authorize Bridge, then back to the Bridge portal. On Standard and Premium, Bridge asks for Lightspeed's view-only permission wherever Lightspeed publishes one. For a few areas — work orders, timeclock, special orders, purchase orders, transfers, inventory counts and product cost — Lightspeed offers no view-only option, so the permission you grant there is broader than what Bridge uses. On those tiers Bridge registers no write tools at all, so nothing can act on it. On Pro you'll authorize a second time to add write access; see "Turning Pro on" below.
3. Bridge runs an initial historical sync of your POS data into an isolated per-tenant database. For an established Lightspeed account this typically takes a few hours to a day. Incremental syncs then run on your tier's cadence — every 24 hours (Standard), every hour (Premium), or every 15 minutes (Pro).
4. Once the initial sync is complete, you can connect Claude (or any MCP-compatible AI client) to Bridge — see the next section.

In Claude (claude.ai or Claude Code), add a custom connector with the following details:

• MCP server URL: https://api.rizolvr.com/mcp
• Authentication: OAuth 2.0 with Dynamic Client Registration (DCR) + PKCE. Claude registers itself automatically; you don't need a static client ID/secret.
• Transport: Streamable HTTP.

When Claude initiates the connection it will redirect you to Bridge's OAuth consent screen (portal.rizolvr.com). Log in with your portal credentials, approve the connection, and you'll return to Claude with an active session. Claude will then ask you to allow each Bridge tool individually — go ahead and allow all of them so the assistant can actually answer questions about your data.

Bridge exposes 99 tools that read your shop, grouped by the way a shop actually works. On Pro, 30 more become available that act on your data — those are listed under "What Pro adds."

• Sales & revenue — daily/weekly summaries, year-over-year comparisons, daypart, attach rate, market basket, taxes, payment mix.
• Inventory & catalog — current stock by shop, aging, actionable dead stock, top SKUs, item search, vendor lead times, variants/bundles.
• Customers — top customers, RFM segmentation, purchase history, customers due for a visit, retention queries, contact info, owned items.
• Work orders & service — open work orders, age distribution, durations, reserved inventory, service revenue breakdown, mechanic productivity.
• Purchasing & transfers — open POs, special orders, transfers in flight, short-shipped lines, vendor returns, PO receiving detail.
• Employees & shop comparison — employee sales performance, hours, multi-shop comparisons.
• Reference & agent helpers — shops, brands, categories, customer types, payment types, workorder statuses; workflow templates and reference documentation.

Some good first questions: "What were my top 10 SKUs last month?", "Which work orders are over their promise date?", "What customers haven't visited in 6 months but spent over $500 last year?"

Pro adds 30 tools that change data in Lightspeed rather than just reading it:

• Items — update prices, costs, metadata and reorder points; create items; archive items; manage tags and shelf stickers.
• Customers — create and update customers, manage customer tags, merge duplicates.
• Purchasing — create and edit purchase orders and their lines, update PO costs, manage transfers.
• Work orders — update status and details, add and remove lines and items, correct labor credits.
• Reference data — create vendors, categories, departments and manufacturers.
• Inventory — small reconciliations.

Write tools only appear for a seat that has been granted the matching scope. A Standard or Premium seat never sees them.

Pro is in beta and opens with an invite code.

1. Ask us for a code — email bridge@rizolvr.com or use the form on our contact page.
2. In the portal, go to Subscription and click the Pro row. Enter your code.
3. Change your subscription tier to Pro.
4. Re-authorize Lightspeed. This step is required. Read-only permission can't be upgraded in place, so Lightspeed asks you to approve the write scopes explicitly. You'll see exactly what you're approving.
5. Grant write scopes to the seats that should have them. Redeeming a code opens the tier; it doesn't hand anyone write access on its own.

A code grants access, not a discount, and it doesn't charge you anything by itself.

Write access is sixteen separate scopes, granted per seat, not one switch:

item:price · item:stock · item:meta · item:create · tag:manage · vendor:create · po:create · po:receive · po:cost · transfer:manage · inventory:reconcile_small · customer:meta · customer:sensitive · customer:create · wo:manage · labor:correct_credit

A seat only sees the write tools its scopes allow. Your service writer can manage work orders and nothing else; your buyer can build purchase orders but not touch prices. The account owner grants and revokes these in the portal at any time.

Every write Bridge makes is recorded in two places.

In your Lightspeed record. Bridge stamps a dated note on the record it touched, in the Internal Note field:

9/6 22:13 - Bridge Updated - etaOut; note; receipt note: QA tz check

Notes accumulate across a session rather than adding a line per call. Your staff can see what the assistant did without leaving Lightspeed.

In your Bridge portal. Every write is logged with the seat that made it, the tool, the timestamp, and the before and after state.

Ask your assistant to undo a change and it calls undo_write, which builds the opposite action and submits it to Lightspeed. The original is then marked rolled back.

Reversible: item prices, costs, metadata and reorder points; customers and customer tags; work orders; archived items; created items.

Not reversible: creating a customer, vendor, category, department, purchase order, or manufacturer. Bridge has no delete for those records — if one gets created in error, remove it in Lightspeed yourself.

Before applying one of these, Bridge tells your assistant that the operation cannot be undone, so you hear it before the record is created rather than after.

How often Bridge syncs your POS data depends on your tier:

• Standard — every 24 hours
• Premium — every hour
• Pro — every 15 minutes, plus an instant refresh after any write

Your tier can be changed from the portal at any time. Lightspeed imposes per-account API rate limits, which is why we sync on a schedule rather than per-query — the assistant queries our database, which is always within at most one sync window of your live POS.

On Pro, any record your assistant changes is re-synced immediately, so you're never looking at a stale copy of something you just changed.

We add and refine tools as we learn what AI assistants do well with Bridge data. MCP clients cache the tool list when they connect, so a new tool won't show up on its own. Your assistant detects this for you — at the start of a conversation it checks how many tools it should have against how many it can see, and if it's behind it'll tell you to refresh. To pick up the latest tools, just disconnect and reconnect the Bridge connector from your client's connector settings. For larger changes we may also email the account owner a short note.

Each tenant's data is stored in a dedicated database of its own, hosted with Amazon Web Services in the United States. The credential that reaches that database is scoped to it alone — no query, however malformed, can reach another customer's data. All traffic is TLS 1.2+, and per-tenant credentials are held in an encrypted secrets store.

Bridge does not log the natural-language questions you ask your AI assistant — those never reach Rizolvr. We log only per-request metadata (tenant ID, tool name, row count, latency) for operations.

Write scopes are granted per seat and can be revoked at any time. Bridge never holds write permission for an account that hasn't explicitly authorized it in Lightspeed.

Full details are in the privacy policy.

• Connection fails or expires: sign in to portal.rizolvr.com and re-authorize Lightspeed if prompted. Then disconnect and reconnect the Bridge connector in Claude.
• Data looks stale or missing: check the portal's sync status. If a recent sync ran, the assistant may need to be told to re-fetch — try rephrasing the question or asking the assistant to call the relevant tool explicitly.
• Seat busy / one-session-per-seat: Bridge enforces one active session per portal seat. If you switch between AI clients within ~60 seconds, the second client may be temporarily refused. Wait a minute and reconnect.
• Token revoked: if you suspect your Bridge access token has been compromised, email bridge@rizolvr.com with the word "revoke" in the subject — we will invalidate active tokens for your account immediately.

Questions, issues, or feature requests: email bridge@rizolvr.com. You can also use the in-product submit_feedback tool from your AI assistant — feedback flows to the same triage queue we read each week.