Safetyculture MCP Server

Connect Safetyculture to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for the SafetyCulture API. This project allows users to ask natural language questions about their SafetyCulture data after providing an API key. The safetyculture mcp server is what makes that connection.

What the server does

This MCP server uses the SafetyCulture Feed API, which provides a simple way to access collections of resources:

• Query SafetyCulture data using natural language
• Analyze inspection data and trends
• Compare safety metrics across time periods and categories
• Visualize inspection trends over time

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• test_api.bat — Run tests in interactive mode (prompts for API key)
• get_inspections — Get SafetyCulture inspections for a specific time period
• get_inspection_trends — Analyze trends in SafetyCulture inspections over time
• compare_injury_reports — Compare injury reports between two time periods
• get_actions — Get SafetyCulture actions for a specific time period
• get_action_details — Get detailed information about a specific action by ID
• Authentication — The Authentication tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Safetyculture's toolset — test_api.bat, get_inspections, get_inspection_trends and 4 more — is a fair guide to whether it matches your workflow. It is maintained by zerubroberts; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.