Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Papershift in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Papershift workforce management: shift plans, working sessions, absences, employees and locations. Public API v1, authenticated with an api_token query parameter.
Try asking
Example prompts for Papershift
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Papershift, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Papershift
Papershift workforce management: shift plans, working sessions, absences, employees and locations. Public API v1, authenticated with an api_token query parameter.
Setup
Getting a token
- Sign in to Papershift as an administrator and open Einstellungen → API (Settings → API).
- Generate a public API token and copy it into
PAPERSHIFT_API_TOKEN. The token is account-wide and carries administrator rights — anyone holding it can read the whole roster, so treat it as a password.
The token travels as a query parameter, not a header: Papershift's public API expects ?api_token=… on every request. AnythingMCP appends it automatically (QUERY_AUTH), so it never appears in a tool's parameters and never has to be pasted into a prompt.
…(continued in the in-app connector instructions)
Prerequisites: PAPERSHIFT_API_TOKEN
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick Papershift and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
papershift_list_users | List employees with their name, e-mail, employee number and the locations they belong to |
papershift_get_user | Read one employee by id: contact details, employment data, assigned locations and tags |
papershift_list_locations | List the locations (Standorte) the account is organised into, with their address and working-area structure |
papershift_list_shifts | Read the planned roster in a date range: who is scheduled where and when |
papershift_list_working_sessions | Read actually worked time in a date range — clock-in and clock-out, breaks and the resulting duration |
papershift_list_absences | Read absences (holiday, sickness, special leave) in a date range with their type and approval state, to explain gaps in the roster |
papershift_list_working_areas | List the working areas (Arbeitsbereiche) inside the locations — the roles a shift can be planned for, such as bar, kitchen or till |
Next steps
Was this guide helpful?
