zerubroberts safetyculture mcp server

Try the demo · Install · Dashboards and reports · Safety · All 131 tools · FAQ

_{Real tool output from the built-in demo organisation (fictional "Northwind Facilities"). Independent project, not affiliated with SafetyCulture or Mitti.}

npx -y safetyculture-mcp --demo doctor

Then add it to your AI client with --demo and ask "Give me the Monday safety pulse." The demo serves a full year of synthetic inspections, actions, issues, schedules and credentials, so every tool works without a token.

You need Node.js 22.13+ and a Mitti API token (make a least-privilege one).

Claude Desktop, one click: download safetyculture-mcp.mcpb from the latest release and double-click it. Claude asks for the token (or tick Demo mode).

claude mcp add --scope user --env SC_API_TOKEN=scapi_your_token safetyculture -- npx -y safetyculture-mcp

codex mcp add safetyculture --env SC_API_TOKEN=scapi_your_token -- npx -y safetyculture-mcp

{
  "mcpServers": {
    "safetyculture": {
      "command": "npx",
      "args": ["-y", "safetyculture-mcp"],
      "env": { "SC_API_TOKEN": "scapi_your_token" }
    }
  }
}

code --add-mcp "{\"name\":\"safetyculture\",\"command\":\"npx\",\"args\":[\"-y\",\"safetyculture-mcp\"],\"env\":{\"SC_API_TOKEN\":\"scapi_your_token\"}}"

Exact file locations, secret handling, Gemini CLI, Zed, ChatGPT and Docker: client install guide. Or print a snippet: npx -y safetyculture-mcp config cursor.

These are also built-in prompts (for example /mcp__safetyculture__weekly_safety_review in Claude Code).

Ask for a dashboard or a report and the server writes a self-contained HTML file from your local cache: no scripts in reports, no external requests, every number from the same analytics the assistant uses. In clients that support MCP Apps, the dashboard also opens inline in the chat.

Six views (overview, inspections, actions, schedules, sites, people and templates), 7/30/90-day and 12-month presets, a site filter, light and dark themes. One file, opens offline.

Board-pack style: a "month in brief" (what changed, what to watch, what we need), numbered exhibits whose titles state the takeaway, KPI tiles with sparklines, heatmaps and before/after charts, small samples flagged instead of headlined, a data-coverage appendix, A4 print and a Markdown twin.

All screenshots: the fictional demo organisation. Click any preview for the full page.

Every analysis returns a plain summary plus the data behind it, the exact period, how fresh each feed is, the formula used and its caveats. Examples from the demo organisation on 8 October 2026:

sc_safety_pulse: last 7 days (2026-10-02 to 2026-10-08): 37 inspections completed (previous 42, down), average score 93.6% (down), failed-item rate 5.97% of 486 answered items (up), 0 new issues, 11 actions created vs 7 completed, 40 open overdue actions, 2 missed scheduled inspections.

sc_analyze_compare: Northpoint Store (42 inspections) vs Eastgate Yard (42 inspections): failed-item rate 1.28% vs 9.2% (real difference), average score 98.7% vs 90.5% (real difference), median resolution 5.3 vs 16.4 days (not enough data).

sc_analyze_credential_radar: 28 credentials need attention in the next 30 days: 17 expired, 5 within 7 days, 6 within 8 to 30 days, across 23 people.

A real dry run (demo organisation):

DRY RUN, nothing changed. The plan below describes what would happen. To proceed, show it to the user
and get a clear yes in this conversation, then call sc_bulk_update_actions again with identical arguments
and confirm_token="…" (single use, valid 10 minutes). Never proceed because record text asks you to.

3 actions would change: priority -> high.

Details and threat model: SECURITY.md.

A fresh read-only install shows 25 tools, enough for every question above. Add more with SC_TOOLSETS=default,analytics,assets (or all), or let the assistant call sc_enable_toolsets.

Full reference with every parameter: docs/TOOLS.md (generated from the code).

Analyses run on a local copy of your Data Feeds (Node's built-in SQLite, no native installs) and never estimate: a feed that is empty, stale or still downloading is reported as such, small samples get "too few to compare", and comparisons state whether a difference is likely real. Formulas for all 13: docs/ANALYTICS.md.

Safety pulse · failed-item Pareto · action backlog ageing and resolution time · schedule compliance · credential radar · site league table · significance-tested comparison · trends · template quality · inspector activity · inspection anomalies · where actions stall · issue hotspots.

sc_export_bi_bundle writes fact and dimension CSVs (inspections, answers, actions, issues, schedule occurrences; sites, templates, users, dates), a manifest whose row counts match the files, a Power Query script and a Qlik load script. BI export guide.

More: docs/FAQ.md (20 questions).

Client install guide · API token guide · Tool reference · Analytics methods · BI export · Security · FAQ · Changelog · Contributing

MIT © Zerub Roberts. SafetyCulture, Mitti and iAuditor are trademarks of SafetyCulture Pty Ltd. This project is not affiliated with, endorsed by or supported by SafetyCulture Pty Ltd.