Osha Compliance Assistant MCP Server

Give Claude instant access to OSHA General Industry compliance knowledge (29 CFR 1910). Ask workplace safety questions and get cited verdicts with

Local serverstdioPython

What is the Osha Compliance Assistant MCP server?

Most developer tooling work still happens through a UI a human drives. Osha Compliance Assistant MCP server moves it into the conversation instead. Give Claude instant access to OSHA General Industry compliance knowledge (29 CFR 1910). Ask workplace safety questions and get cited verdicts with regulation sections and corrective actions.

The short version

  • "Do I need guardrails on a 4-foot platform?" → ✅ YES - Section 1910.23(c)(1)
  • "Can I store propane cylinders near an exit door?" → ❌ NO - Section 1910.253(b)
  • "Is automatic restart after a power outage allowed on saws?" → ❌ NO - Section 1910.213(a)(9)

The tools it exposes

The server publishes 6 tools. What each one is for:

  • Tier — Daily Calls
  • Sandbox — 10/day
  • Developer — 500/day
  • Team — 2,000/day
  • Enterprise — 10,000/day
  • compliance_check — Check whether a workplace scenario complies with OSHA General Industry standards

Getting it running

Installation goes through your MCP client rather than a global install: point it at mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: OSHA_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.

How it compares

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. Osha Compliance Assistant's toolset — Tier, Sandbox, Developer and 3 more — is a fair guide to whether it matches your workflow. It is maintained by contextkits; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Osha Compliance Assistant's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • 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.

Available tools

ToolWhat it does
TierDaily Calls
Sandbox10/day
Developer500/day
Team2,000/day
Enterprise10,000/day
compliance_checkCheck whether a workplace scenario complies with OSHA General Industry standards.

How to install the Osha Compliance Assistant MCP server

{
  "mcpServers": {
    "osha-compliance-assistant": {
      "command": "uvx",
      "args": ["mcp"],
      "env": {
        "OSHA_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OSHA_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Osha Compliance Assistant to Tier.
  • Use Osha Compliance Assistant to Sandbox.
  • Use Osha Compliance Assistant to Developer.

Frequently asked questions

It connects Osha Compliance Assistant to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Tier, Sandbox, Developer, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Osha Compliance Assistant directly.