Back to Guides

Connect HR WORKS to ChatGPT — German HR via MCP

Expose HR WORKS to ChatGPT via MCP. Query employees, absences, sick leaves, working times, projects, and applicants in natural language. Pre-built v2 adapter.

Pre-built adapter available on AnythingMCP Cloud

Skip the self-hosted setup — install this adapter in one click with a free trial. No credit card required.

Install on Cloud — Free Trial

Connect HR WORKS to ChatGPT

HR WORKS is the Freiburg-based HR/payroll SaaS used by ~20,000 DACH SMBs. With AnythingMCP you expose HR WORKS to ChatGPT via MCP — your Custom GPT or MCP-native ChatGPT client can answer absence, working-time, and recruiting questions directly from the live HR data.

Quick Setup

git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d
  1. In HR WORKS: Settings → API → Generate Access Key
  2. Exchange for a JWT (15-min lifetime):
    curl -X POST https://api.hrworks.de/v2/authentication \
      -H 'Content-Type: application/json' \
      -d '{"accessKey":"...","secretAccessKey":"..."}'
    
  3. Import HR WORKS in http://localhost:3000/connectors/store and paste the JWT into HRWORKS_TOKEN
  4. (Optional) Sandbox: set HRWORKS_BASE_URL=https://api.demo-hrworks.de
  5. Assign the connector to an MCP server

Connect to ChatGPT

{
  "mcpServers": {
    "hrworks": { "url": "https://your-anythingmcp-instance.com/mcp" }
  }
}

ChatGPT MCP support is rolling out via Custom GPT → Actions and the upcoming MCP-native client. The endpoint must be HTTPS for ChatGPT to reach it from the public internet.

Use Cases

  • "Show next week's absences for the engineering org unit" — line-manager triage
  • "Total sick days by department for Q1" — exec-dashboard answers
  • "Working-time totals for personnel number 1042 in March" — payroll prep
  • "List remote-work entries for Müller, Hans this month" — hybrid policy check
  • "Pipeline for the Berlin Frontend job posting" — recruiter handoff

Pro Tips for ChatGPT

  • Limit dates: HR WORKS caps beginDate/endDate at 1 year (31 days with interval=days) — phrase queries within those windows
  • Identifiers: most person endpoints accept either personnel number or username — tell ChatGPT which one you'll use
  • Token tokens: every tool call shows up in ChatGPT's billing — use hrworks_health_check for connectivity tests instead of expensive list calls
  • Token lifetime: refresh HRWORKS_TOKEN via cron + AnythingMCP admin API for long-running custom GPTs

Related Guides