Someone noticed a problem at one of your sites. Who will check it? When? Will anyone remember about it tomorrow?
monitorQA now connects to Claude, Anthropic's AI assistant. Claude checks new Issues every hour and turns each one into an audit for the right person.
Here's what that gives you:
- Anyone can report a problem. Employees, customers or visitors scan a QR code at the site, answer a few questions and click Create. They get a reference number for their Issue.
- Every Issue becomes an audit. Claude reads the Issue, picks the template that fits the problem and creates an audit for that site, due today.
- The auditor knows what to look for. The text of the Issue goes into the audit as instructions: "Issue 184404342 reported on Nov 5: broken refrigerator. Please check this during the audit."
- Nothing is handled twice. The audit is linked to the Issue, so Claude skips it on the next run.
- Unclear Issues stay with you. If the text is a test or no template fits, Claude doesn't create anything and lists the Issue for your review.
How to set up
1. Create an Issue type and a QR code
- In monitorQA, click Create Issue Type. Enter a Name, for example "Problem report", and a Description.
- In Questions, add a question such as "What happened and where?" Claude picks the audit template from the answer, so ask people to describe the problem.
- Go to Issues and select QR codes.
- Click Create QR Code at the top right.
- Choose the Issue Type and the site. Choose a specific site rather than all locations, so every Issue is linked to the right site.
- Click Create.
- Print the QR code or save it as an image, and place it where people notice problems: "Noticed a problem? Scan here."
When someone scans the code, the Issue form opens in their mobile browser. They answer the questions, click Create and see a confirmation with a reference number. The Issue appears in Issues under Pending Issues.
2. Ask monitorQA to enable MCP
Contact monitorQA support or your account manager and ask them to enable MCP for your company. This is done once for the whole company.
3. Install Claude
- Download the app at claude.ai/download or use claude.ai in your browser.
- Sign in. A paid Claude plan is required.
4. Connect monitorQA
- In Claude, open Settings, then Connectors.
- Click Add custom connector and enter:
- Name: MonitorQA
- URL: https://mcp.monitorqa.com/mcp
- Click Continue. Don't change anything on the next screen, just click Add.
- Click Connect. A monitorQA page opens in your browser.
- Sign in to monitorQA if asked.
- Leave Allow making changes on. Claude needs it to create audits.
- Click Allow access. You'll see "Access granted".
5. Check that it works
Open a new chat and type: "Show my open Issues in monitorQA." If you see a list of Issues, monitorQA is connected.
6. Create the scheduled task
- Decide who gets the audits: one specific person, or any user with access to the site. You can see who has access on the site's Access tab in monitorQA.
- In a new chat, type "Create a scheduled task that runs every hour with this prompt:" and paste the text below. Replace the parts in angle brackets.
- Check the name and schedule Claude suggests and click Schedule.
Use the MonitorQA connector. Task: create an audit in monitorQA for every NEW open Issue. Act without asking for confirmation.
Settings:
- Assignee: <full name of the user> OR "any user with access to the site".
- Cutoff: only Issues created on or after <start date and time, UTC>. Ignore older Issues.
Steps:
1. search_issues with status "pending", from_date = yesterday (UTC), page_size 100, all pages. Keep only Issues created on or after the cutoff.
2. For each, call get_issue. If the Issue already has a linked audit, skip it.
3. Pick the audit template (templateType 0) whose name clearly fits the problem described in the Issue. If nothing fits or the text is a test, create nothing and report the Issue as "needs review".
4. Choose the assignee. If a name is set above, find that user with list_users and use their id. If it says "any user with access to the site", call get_audit_object_access for the Issue's audit object and pick one of those users at random, preferring users with access through a job title over users with access only through the Admin role. If nobody has access, create nothing and report the Issue as "needs review".
5. create_audit: the Issue's audit object, the chosen template, end_date = today end of day (UTC), the chosen assignee, name "Issue <number>: <short problem>", auditor_hint "Issue <number> reported on <date>: <summary>. Please check this during the audit."
6. Link the audit with update_issue (full update): keep the Issue's current priority, due date and assignees; audits_ids = existing linked audits + the new one.
7. If create_audit succeeds but update_issue fails, report it clearly.
At the end, list the audits you created (Issue number, site, template, assignee, audit name) and any Issues that need review. If there was nothing new, say "Nothing new".
The cutoff keeps Claude from creating audits for all your old Issues at once. Set it to the moment you start.
7. Test the task
- Scan the QR code and report a clear problem, for example "Broken refrigerator".
- Run the task once manually.
- In monitorQA, the assignee has an audit "Issue <number>: …" due today, and the Issue shows it as linked.
- Report "Test". No audit is created, and the run result lists the Issue for review.
Good to know
- Where do I see the results? In the scheduled task's run history. Each run shows the audits it created and the Issues that need review.
- Your computer can be off. Scheduled tasks run in the cloud.
Stop the automation
Pause or delete the scheduled task in Claude. To revoke access completely, in monitorQA click your name in the bottom-left corner, open Connected apps and revoke Claude.
Start with one site and one QR code. Questions about setup? Reach out to our support team.
