Personio MCP Server

Time off, employees and attendance in Personio, handled by your agent.

호스팅형 MCP 서버

npx add-mcp 'https://cotlet.dev/mcp/v1/personio'

Claude Code, Codex, Cursor 등에 설치됩니다

문서

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Personio API and MCP server: Let your AI agent clear your Personio Inbox.

Personio has an official MCP server in beta and a public REST API (checked 27 Oct 2026). The beta "isn't available for everyone yet", an Administrator switches it on, and it reads profiles, time off and pay and can request time off. Its help page lists approving time off as "coming soon". The API needs the Core Pro plan and company-wide credentials, and has no approvals endpoint. Cotlet runs 13 Personio tools hosted, Inbox approvals included, over MCP and REST.

Time off, employees and attendance in Personio, handled by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Personio. Personio is a trademark of its owner. If Personio's own integrations cover what you need, use them first.

What can you automate in Personio?

  • Approve time off by your rule
  • Book a closing day for a team
  • Post who is off next week
  • Fill in missing attendance
  • Update a profile after a move
  • Check balances before approving

Does Personio have an MCP server or an API?

  • API credentials ignore role permissions: Personio warns that anyone holding them "can retrieve almost all data from the Personio account through the API".
  • The official MCP has no attendance or profile-update tools, and its write access is a second admin toggle that is off by default.
  • Zapier (6 triggers, 7 actions) and the GitHub MCP servers run on Personio API credentials, so none of them approves or rejects an Inbox task.
What you needPersonio API (Core Pro)Personio MCP (beta)Cotlet
Approve or reject Inbox requestsNoComing soonYes, after your OK
Read employees, time off and balancesYesYesYes
Request or book time offYesIf writes are onYes, after your OK
Log attendance, update a profileYesNoYes, after your OK
Follows your own roleNo, company-wideYesYes, your login
What you need firstCore Pro and an adminBeta access and an adminYour own login

Checked 27 Oct 2026. Sources: Personio MCP server, Beta access overview (Personio Help), Generate and manage API credentials (Personio Help), Overview of Personio plans and apps (Personio Help), Personio API reference, Zapier (Personio Help)

How does Cotlet connect to Personio?

  1. Sign in to Personio. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Personio password, and no approval, rejection, booking or profile change is saved before you approve it.

Connect Personio to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Sign in to Personio in a Cloud Browser. Create a Cotlet account, open Personio in its Cloud Browser, sign in as the manager or HR person who approves requests and press Enable for agents.
  2. Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in your agent's MCP server or connector settings.
  3. Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console.

https://cotlet.dev/mcp/v1 carries every app you enable on Cotlet, Personio with them. If you enable Personio after connecting, refresh the connector to load its tools. No Personio admin and no API credentials are involved.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: personio_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: personio_write

How to use the Personio REST API

Create your Cotlet API key

Create a Cotlet API key with access to Personio and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Personio in Cotlet and enable it for agents. Account access: Your own Personio account (approver rights to approve requests, Edit or Propose permissions to book time off or hours).

Make your first Personio API request

REST:

curl "https://cotlet.dev/api/v1/personio/employees?limit=100" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read employees and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "personio",
  "tool": "list_employees",
  "result": {
    "employees": [
      {
        "employee_id": "emp_2041",
        "name": "Maja Kowalska",
        "team": "Marketing",
        "position": "Content Lead",
        "supervisor": "Tom Becker",
        "status": "active",
        "hired_at": "2024-03-01"
      }
    ],
    "next_cursor": "eyJvZmZzZXQiOjEwMH0"
  }
}

Lists employees you may see in Personio, newest first. Filter by team, status or a name fragment.

Only the attributes your role may read are returned; others come back empty. Pages hold up to 100 employees; pass next_cursor back as cursor for the next page.

limit: Items per page, 1 to 100. Default 100.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Personio workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestTime off periods in a date window, with status, newest first. Use list_time_off in your configured team report.
MakeHTTP > Make a requestAttendance periods of employees in a date window. Use list_attendance in your configured team report.
Python or Node.jsREST APIRequests waiting for you in the Personio Inbox. Use list_approval_requests in your configured team report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Personio; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Personio API endpoints and MCP tools

Inbox approvals

Time off, attendance and employee data tasks where you are the approver, delegated ones included. With more than one step, an approval passes the request to the next approver.

  • List approval requests (list_approval_requests, read): Requests waiting for you in the Personio Inbox.
  • Get an approval request (get_approval_request, read): Details of one request: dates, balance after approval, team overlap.
  • Approve a request (approve_request, write, asks first): Approve one request from your Inbox.
  • Reject a request (reject_request, write, asks first): Reject one request from your Inbox, with an optional comment.

Time off and balances

Types and balances follow each person's time off policy. With Propose permissions a booking goes to approval; with Edit it is saved at once.

  • List time off types (list_time_off_types, read): Time off types you can use, with their unit (days or hours).
  • Get a time off balance (get_time_off_balance, read): Remaining balance of one employee for one time off type.
  • List time off (list_time_off, read): Time off periods in a date window, with status, newest first.
  • Request time off (request_time_off, write, asks first): Request time off for yourself or, with the right permission, for another employee.

Attendance

Work periods and breaks from the Attendance tab. Periods of one person cannot overlap.

  • List attendance (list_attendance, read): Attendance periods of employees in a date window.
  • Log attendance (log_attendance, write, asks first): Add a work period with an optional break to an employee's attendance.

Employees

Only the attributes your role may see or edit. Salary and other hidden fields stay out.

  • List employees (list_employees, read): Employees with name, team, job title, supervisor and status, newest first.
  • Get an employee (get_employee, read): One employee profile with the fields your role may read.
  • Update an employee (update_employee, write, asks first): Change fields on an employee profile.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/personio-api-mcp-server#tools

Who can see my Personio session, and how do I revoke it?

  • What we store. Your signed-in Personio profile, AES-256-GCM, on servers in Finland. Never the password.
  • What your agent gets. 13 Personio tools. No cookie, no login, no API credentials.
  • What the session sees. What your Personio role sees: a supervisor gets the reporting line, not the whole company.
  • What no tool touches. Payroll, compensation, documents, recruiting, approval rules and settings.
  • If Personio asks for a token. You get a sign-in link and enter the emailed code yourself. We never do.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.

Personio data is employee personal data under GDPR. Cotlet logs the time, tool and status of each call, never the payload. The Cotlet site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Reads your Inbox. Time off tasks waiting for you, delegated ones included.
  2. Checks each request. Balance after approval and team overlap, from the request page.
  3. Waits for your OK. Every approval sits in your Cotlet console before Personio sees it.
  4. Reports back. Approved, and left for you with one reason each.
ActionUndo
Approve time offEdit or delete the period; the employee already has the email
Reject a requestNo; the employee sends a new one
Book time off for someoneDelete the request; with approval it was pending
Log attendanceEdit or delete the period
Update a profileSet the old value back

All 5 write tools ask first, because each one changes what an employee or payroll sees. Reads run at once. For a daily run you can switch the wait off per tool, for example for approve_request once your rule has proved itself.

After you decide, Personio emails the employee. If someone later changes the dates of an approved request, it goes back to pending and lands in your Inbox again.

MCP call:

{
  "name": "request_time_off",
  "arguments": {
    "employee_id": "emp_2041",
    "time_off_type": "Vacation",
    "start_date": "2026-12-24",
    "end_date": "2026-12-26"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/personio/time-off/request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"employee_id":"emp_2041","time_off_type":"Vacation","start_date":"2026-12-24","end_date":"2026-12-26"}'

Response:

{
  "time_off_id": "to_93a1",
  "employee_id": "emp_2041",
  "time_off_type": "Vacation",
  "start_date": "2026-12-24",
  "end_date": "2026-12-26",
  "days": 3,
  "status": "pending"
}

Scripts and cron jobs call the same tools over REST at /api/v1/personio, with one key and one price, and need no Core Pro plan. A call your Personio role cannot make returns an error and costs nothing. Each tool row lists its REST path.

How much does the Personio MCP server cost?

About $20 a month for HR in a company of about 90 people, 3,470 credits. Works on Core; the Personio API needs Core Pro.

JobCallsCredits
Time off queue by your rule, each workday6 × 221,320
Team absence digest, weekly2 × 480
Fill in missing attendance, weekly8 × 4320
Profile change after a move or promotion2 × 480
Book a bridge day for one office of 1517 × 1170
Cloud Browser, 30 days1,500
Total3,470
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No Core Pro plan, API credentials or MCP beta needed

Personio has about 16,000 customers and 1.5 million employees (2026), about 94 people each. The month assumes about 60 time off requests (8 a person a year), a weekly attendance check and one office-wide booking. Dollars at the $29 pack rate.

Personio MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
borgels/mcp-server-personioTypeScript, Apache-2.0. An employee profile (own absences, attendance, documents) and an HR profile (persons, absences, attendance, projects). 0 stars, last push 23 Oct 2026.Needs Core Pro API credentials; its README says approving pending absences has no public API.
NikolaiGoMedicus/personio-mcp-serverTypeScript, MIT. Employees, attendance, absences, documents and recruiting. 1 star, last push 26 Jul 2026.Same credentials in environment variables, readable by any program on your computer.
StackOne, KnitHosted Personio MCP servers with 54 and 25 actions, for software companies building agents into a product.On the public API, so no Inbox approvals.
Composio10 read tools: absences, attendance, documents, persons, projects.Reads only.

If you only need to sync people, absences and hours with another system, Zapier or a GitHub server on the API does it; custom credentials need Core Pro and an admin. If your company is in the MCP beta, the official server answers questions about profiles and pay. If the agent should clear your Inbox, book for a team and fix hours with your own rights, Cotlet does that hosted.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273) and trading since 2019, like Personio an EU business. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Personio tools go to contact@cotlet.dev.

Personio API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Personio under Integrations in the console and sign in to Personio in its Cloud Browser. The trial starts when you sign up, no card needed.

How do I connect Personio to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Personio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Personio account through Cotlet, in their phone apps too.

What can ChatGPT do in Personio?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Personio: auto-approve time off requests; book time off for several employees; send a weekly team absence digest. You ask in plain words, and anything that reaches other people waits for your OK first.

Which Personio permissions does my agent need?

The agent acts with your own permissions. To approve time off you need to be an approver with View permission for the time off type; to book hours or time off for others you need Propose or Edit permissions, and Edit skips approval. Personio's own MCP beta works the same way: each person's access follows their permissions.

Does Personio approve time off automatically?

Only through approval rules. An Administrator sets a default rule and group rules per time off type, and a request with no applicable approval step is approved at once. Rules choose approvers; they do not check balance or team overlap.

Should I wait for Personio's own MCP server?

If your company is in the beta and you only need answers about people, time off and pay, use it: it is free with Personio. Approving time off is listed there as coming soon, with no date (checked 27 Oct 2026). Cotlet adds approvals, attendance and profile updates today, without an admin switch.

Does Personio have webhooks?

Yes. API v2 has webhooks, set up with Core Pro API credentials. Cotlet sends no webhooks; run your agent on a schedule to work the Inbox.

Is the MCP server different from the REST API?

Only in how you call it. Both have the same 13 tools, inputs and answers, one API key and one price. Agents use MCP; cron jobs and scripts use REST.

Is Cotlet affiliated with Personio?

No. Cotlet is independent and not affiliated with Personio SE & Co. KG.

Can I use the Personio API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.