An AI assistant for your QR codes and customer feedback

01

What you can ask it

The questions people actually have about their QR codes are comparisons and lists: which codes were scanned most this month, which ones nobody has scanned since the print run, how this week compares with the last, which placement of a campaign is doing the work. An assistant answers those in a sentence instead of a dashboard you have to read, and it names the codes so you can check.

Feedback works the same way: how a survey is trending, which question scores lowest, how many people answered since the menu changed. Through MCP an assistant gets the numbers — counts, choices, the spread per question, how many people wrote a comment — and never the text of a comment. The built-in assistant can read the most recent written comments, for the same people the response inbox shows them to, so it can tell you in a sentence what they are about.

• The most-scanned and the silent codes, by name
• This period against the last, for one code or the whole workspace
• Survey scores, and the spread behind an average
• Scan details limited by the workspace’s own privacy settings

02

What it can change, and who says yes

In the workspace the assistant never acts on its own. It proposes: a new code, a card template written from your description, a survey’s questions, a new destination for a dynamic code, publishing or archiving. Each arrives as a card that says what will happen, and nothing changes until somebody presses it — with that person’s own role, so a viewer can read a proposal but not carry it out.

Over MCP the assistant calls the tools its key or sign-in allows. Every tool that writes is marked as one, and archiving is marked as destructive, so a client that honours those markers asks you before it runs them. There is no tool that deletes a code: archiving is as far as it goes, and an archived code can be restored.

• Built in: create URL, Wi-Fi, text, vCard and app link codes; draft card templates and surveys
• Built in and over MCP: point a dynamic code somewhere new, publish, archive
• Over MCP: create URL codes as drafts, and start a CSV import that is a dry run unless you say otherwise
• Neither: delete a code, invite people or change who has access

03

Two ways to connect an outside assistant

The MCP server has one address: https://api.mosaqo.app/v1/mcp. The simplest way in is an API key. An owner or admin creates one under Bulk & API, ticks what it may do, and pastes it into the client. A key can carry an expiry date and an IP allow-list, and revoking it stops it at once.

The other way is a sign-in. The client registers itself and opens a Mosaqo page, where an owner or admin approves it for one workspace. It then appears under Connected assistants, and Disconnect ends it immediately. Either way, one credential reaches one workspace.

• qr:read and qr:write for codes, exports:read for their images
• analytics:read for scans, reviews:read for places and survey reports
• bulk:write and webhooks:write only when you need them
• A tool outside the access you granted is not offered to the assistant at all

04

Start with less access than you think you need

A read-only key answers most of what people want from an assistant: reports, comparisons, the list of codes that need attention. Give it qr:read and analytics:read, use it for a week, and add qr:write when there is a change you actually want made from a conversation.

Keep a separate key for each tool and each person. A key that leaks, or an experiment you have finished with, can then be revoked without touching anything else.

05

Limits worth knowing before you rely on it

The built-in assistant answers up to 60 questions per workspace an hour and 300 a day, and it stays on the subject of the workspace: an unrelated question gets a polite refusal. Each person can hide it from their own workspaces in Preferences.

Over MCP, each key or sign-in can make 600 requests a minute, a guard against a runaway loop rather than a plan limit. Scan analytics cover dynamic codes only, because a static code never passes through Mosaqo once it is printed.