Bridge by Rizolvr — Documentation

Bridge is a hosted Model Context Protocol (MCP) connector that gives a retailer's AI assistant secure, read-only access to their Lightspeed Retail (R-Series) point-of-sale data. Your AI 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.

Bridge is offered as a paid subscription ($39.99–$79.99/mo cadence tier, with an optional per-seat add-on). It is operated by Rizolvr LLC (Wyoming, USA) on AWS infrastructure in the United States (us-west-2).

1. Sign up at portal.rizolvr.com. Pick a sync-cadence 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 with read-only scopes, then back to the Bridge portal.
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 chosen cadence (24h, 8h, 4h, or 1h).
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 75 purpose-built tools across these areas:

• 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?"

You can choose how often Bridge syncs your POS data:

• 24h — once a day (basic plan)
• 8h — three times a day
• 4h — six times a day
• 1h — every hour

Cadence 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 cadence window of your live POS.

We add and refine tools as we learn what AI assistants do well with Bridge data. When a tool list changes materially, we email the account owner with a short note and a one-line refresh instruction. Most MCP clients pick up the new tool list on the next reconnect — disconnect and reconnect the Bridge connector from Claude's connector settings to see updates immediately.

Each tenant's data is stored in a dedicated logical database on AWS Aurora Serverless v2; the tenant's database user is confined to that database alone — no cross-tenant access is possible. All traffic is TLS 1.2+. Per-tenant credentials are encrypted in AWS Secrets Manager.

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.

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.