Ask your AI assistant about your frontline operations.

Audits and compliance

Pull submitted reports with their scores, questions, answers and photos over any date range, and summarise compliance by site, department or questionnaire.

Issues and corrective actions

Filter findings by status, severity, priority, site, assignee or due date, and read the full activity trail of any single issue to see how long it sat where.

Sites, people and plans

Resolve site, user, department and questionnaire names into records, and check audit schedules — planned, in progress, completed or overdue — across a date range.

Sites

• list_sites — stores, branches and outlets with their departments, city and timezone. Filter by site name, department, city or location.
• get_site — one site in full: address, timezone, departments and assigned users.

Audit reports

• list_reports — submitted reports with scores and completion metadata. Filter by site, department, questionnaire, submitter, city, status and date range.
• get_report — one report in full: every question, answer, score and attached photo.

Issues

• list_issues — findings and corrective actions. Filter by status, severity, priority, origin, site, department, category, creator, assignee, city and date range, with sorting.
• get_issue — one issue in full: status, severity, priority, assignees, due date, linked report and photos.
• get_issue_status_history — the chronological activity trail, with real status transitions separated from comments and reassignments.

Users

• list_users — active users with role, email and status, searchable by name or email.
• get_user — one user: name, email, role, status, language and onboarding state.

Questionnaires

• list_questionnaires — audit checklists in your organization, most recently updated first, with the question count of the latest version.

Schedules

• list_schedules — the audit plan over a date range, each schedule with its date and status (not started, in progress, completed or overdue), plus per-status counts.

Departments

• list_departments — departments defined in your organization, including disabled ones, with their status.

Built to answer accurately

Responses are shaped for assistants, not just for programs: the date window actually applied comes back with the results, partial pages say so, and filters backed by a fixed set of values are declared as such — so an assistant cannot quietly answer “none” when it means “not that filter”.

No writes, ever

All 12 tools are reads. Nothing in the MCP surface creates, edits or deletes a site, report, issue, user or schedule.

One organization per connection

Every request is bound to the organization that authenticated it. No tool can reach another organization's data, whatever it is asked.

Scoped consent

Seven scopes, one per data domain. A token missing a scope is refused for the tools that need it, so you can grant issues without granting users.

Modern OAuth

OAuth 2.1 with PKCE (S256), dynamic client registration, short-lived access tokens, refresh token rotation and revocation.

No copy of your data

The server holds no cache or copy of your records. Each tool call reads live from the platform and returns the result to your assistant.

Fair-use limits

Requests are rate limited per organization on the same budget as the REST API — one tool call costs one request. Tool discovery is not metered.