What you can ask Claude
Ask in your own words, in Claude on the web, on desktop or in Claude Code. Claude picks the Worklayer tool that fits and answers from your data as it is at that moment. Some examples:
- Who's away in the Sales team next week?
- Who reports to Maria Becker, and which department is she in?
- How many vacation days do I have left this year?
- Request vacation for me from 2 to 6 March.
- Show the approvals waiting for me, and reject Jonas's team dinner expense because the receipt is missing.
- Create a task to prepare the laptop for Monday's new hire and assign it to me.
- Submit my mileage: 120 km to the client in Leipzig and back on Tuesday.
- How did headcount and turnover change by department this year?
The analytics questions work for admins. Everyone else gets answers within what their role shows them in Worklayer.
What Claude can change
The server has 58 tools, each marked as reading or changing data. Only these change anything, and only where your role allows it:
- Time off: request, change or cancel time off, after a check against the leave policy and existing absences.
- Tasks: create and update tasks, add comments.
- Approvals: approve or reject, with a reason for a rejection.
- Expenses: submit, change or cancel expenses, after a preview of the exact amounts, per diem and mileage.
People, org and analytics data is read only. There are no tools for payroll, payments or editing employee records. Because the changing tools are marked as such, Claude asks you before it runs one.
Sign-in and permissions
- You sign in to Worklayer in your browser with OAuth. Claude receives a token, never your password, and there is no API key to manage.
- Claude acts as you. It sees and changes only what your role allows in Worklayer: an employee's Claude sees what that employee sees, an admin's sees what the admin sees.
- Each person connects their own account. On Claude's Team and Enterprise plans, an owner adds the connector first, then every member signs in with their own Worklayer account.
- Worklayer logs every tool call with the person and the tool.
- What a tool returns is sent to Claude and handled under Anthropic's terms for your Claude plan.
- To disconnect, remove the Worklayer connector in Claude.
Set it up in three steps
- 1.
Copy the server URL
It is on the MCP setup page, with the exact steps for Claude, Claude Code and other AI tools.
- 2.
Add Worklayer as a custom connector
In Claude, add a custom connector named Worklayer with that URL. In Claude Code, it is two commands in the terminal.
- 3.
Sign in and ask
A browser window opens. Sign in with your Worklayer account, then ask your first question.
Claude or Worklayer's own agents
Claude works with Worklayer while you chat, as you. Worklayer's own AI agents run inside Worklayer without anyone chatting: on a schedule or when something happens, such as a new hire, within the permissions an admin grants them.
Questions
Only what you can see yourself. The server applies your Worklayer role to every call, so asking through Claude never widens your access. An admin's Claude sees what the admin sees.
The tools that change data are marked as such, so Claude asks you before it runs them. A time-off request is checked against the leave policy first, and an expense is shown with its exact amounts before it is submitted.
Yes. It works in Claude on the web, in the desktop app and in Claude Code. In Claude Code you add it with two terminal commands. Setup steps
Yes. The MCP server is part of every plan, including the free plan for companies of up to 3 employees, including the admin. See pricing
Yes. The same server connects ChatGPT, Codex, Cursor, VS Code and any MCP client that supports remote servers with OAuth sign-in. Connect another AI tool