safe-mind-tools
# Safe Mind Developer Tools
Official CLI and MCP server for [Safe Mind](https://www.safe-mind.de) - the platform
for the legally required psychological risk assessment (Gefährdungsbeurteilung
psychischer Belastung, GBU Psyche) in Germany.
| Package | npm | Purpose |
| --- | --- | --- |
| [`cli/`](./cli) | [safe-mind](https://www.npmjs.com/package/safe-mind) | Terminal client for the Safe Mind Public API v1 |
| [`mcp/`](./mcp) | [safe-mind-mcp](https://www.npmjs.com/package/safe-mind-mcp) | MCP server for AI assistants (Claude, ChatGPT, Gemini, Cursor, ...) |
## Quick start
```bash
npm install -g safe-mind
safe-mind login --email you@example.com --password '...'
safe-mind surveys create --start 2026-10-01 --weeks 4 --employees 220 \
--department "Produktion" --department "Verwaltung"
```
MCP (any MCP client):
```json
{
"mcpServers": {
"safe-mind": {
"command": "npx",
"args": ["-y", "safe-mind-mcp"],
"env": { "SAFE_MIND_API_KEY": "sm_live_..." }
}
}
}
```
## Documentation
- API reference and examples: https://www.safe-mind.de/developers
- Anonymity: analytics endpoints only return aggregated results; groups below the
minimum group size are filtered server-side.
## License
MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource+action: auth lifecycle (register, verify_email, get_api_key, me), read-only listings (surveys, departments, locations), creation (department, location, survey), and result retrieval (get_survey, get_analytics). Descriptions even cross-reference the right sibling tools (e.g. list_surveys points to get_survey and get_analytics). No two tools can be reasonably confused.
Nearly all tools follow a predictable safe_mind_<verb>_<noun> pattern (list_surveys, create_department, get_analytics), and the shared prefix is applied uniformly. The only deviation is safe_mind_me, which lacks a verb and breaks the pattern slightly, plus register/verify_email omit an explicit noun.
12 tools is well within the ideal 3-15 range and each tool earns its place, covering auth, segmentation setup, survey lifecycle, and analytics without redundancy. Nothing feels padded or missing for the stated scope.
The surface covers the full intended workflow: onboarding/auth, department and location setup, survey creation and retrieval, and aggregated analytics, with idempotent creates. There is no update or delete for surveys, departments, or locations, but the descriptions explicitly note these are intentionally unavailable via the API, so the gaps are documented rather than dead ends.