ChecQR

ChecQR is an operational record-keeping platform.

Teams scan a QR code to complete checklists such as food safety checks, equipment inspections and visitor sign-ins on their phones, and managers review results, alerts and reports in the ChecQR dashboard. This connector lets your AI work with your ChecQR organisation using your own ChecQR account.

MCP connector

Server URL: https://mcp.checqr.net/
Login: API key
Protocol: MCP 2025-11-25
Instructions: ChecQR is connected. returns the organisations the user can access and which one is active. These tools manage checklist structures, show historical results and show organisation details. Results: (all checklists, by time range), (one checklist, by time range), (single period detail) and (individual answers for a period). Timestamps are Unix milliseconds; returns the current date and time. Periods identify checklists by checklist_id; returns the names. Each period includes a progress field with progress_percentage, completed_answers and total_answers. returns the organisation's settings and returns who has access. Questions are required by default; required set to false makes a question optional. Follow-on questions (shown only when a specific answer is given) take two calls: on the parent question returns a parent_question_id and parent_action_id, and with those two IDs creates the follow-on question. An answer action has no effect until a follow-on question is attached to it. ChecQR has two separate mechanisms for conditional questions. (1) creates a trigger on one question that fires when that question is answered a certain way, either revealing a follow-on question (via with parent_action_id) or raising an alert (via action_type). (2) hides one or more questions until rules are satisfied; a rule can reference the answer to any earlier question on the checklist and/or restrict visibility to specific check windows (e.g. a morning shift). Conditions based on a non-adjacent question, a check window, or several combined rules need ; covers one question revealing the next question or raising an alert. Processes (multi-stage workflows of checklists) are managed with , , and . replaces the whole stages and parameters lists, so stages left out of the call are removed; returns the current stages with their stage_id values. Process runs are shown by and .

Tools

Reads data26

Changes data20

Deletes or can't be undone28

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.checqr.net/

API key

Protocol

MCP 2025-11-25

Instructions

ChecQR is connected. returns the organisations the user can access and which one is active. These tools manage checklist structures, show historical results and show organisation details. Results: (all checklists, by time range), (one checklist, by time range), (single period detail) and (individual answers for a period). Timestamps are Unix milliseconds; returns the current date and time. Periods identify checklists by checklist_id; returns the names. Each period includes a progress field with progress_percentage, completed_answers and total_answers. returns the organisation's settings and returns who has access. Questions are required by default; required set to false makes a question optional. Follow-on questions (shown only when a specific answer is given) take two calls: on the parent question returns a parent_question_id and parent_action_id, and with those two IDs creates the follow-on question. An answer action has no effect until a follow-on question is attached to it. ChecQR has two separate mechanisms for conditional questions. (1) creates a trigger on one question that fires when that question is answered a certain way, either revealing a follow-on question (via with parent_action_id) or raising an alert (via action_type). (2) hides one or more questions until rules are satisfied; a rule can reference the answer to any earlier question on the checklist and/or restrict visibility to specific check windows (e.g. a morning shift). Conditions based on a non-adjacent question, a check window, or several combined rules need ; covers one question revealing the next question or raising an alert. Processes (multi-stage workflows of checklists) are managed with , , and . replaces the whole stages and parameters lists, so stages left out of the call are removed; returns the current stages with their stage_id values. Process runs are shown by and .

Tools