MCP connectorsPersonio

Personio MCP: connect Personio to Claude and ChatGPT

Ask Claude or ChatGPT who is off next week, how many sick days a team has had this quarter or which new starters join in November. The answer comes straight from Personio, without building a report or messaging HR.

We build the connector for your company on Personio’s own API. It only reads, it sees only the fields your Personio admin allows, and your company decides which groups get it. HR data is sensitive, so salary details stay out unless you choose otherwise.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Personio in Claude and ChatGPT

HR

Answers without a custom report

Headcount by office or department, new starters, leavers and probation dates, asked in plain words instead of built as a report.
Managers

Who is in this week

Approved time off and sick leave for your team, so you can plan the week before the Monday meeting.
Operations and finance

Hours and absence in one view

Attendance and absence per team and period, summarised the way you ask, ready for a staffing plan or a month-end check.
Recruiting

Where the hiring stands

Open roles and their applications, which ones are new and how many are in each stage.
Examples

Ask it like this

  • “Who in the London office is off next week?”

  • “How many sick days has the customer support team had this quarter?”

  • “Which new starters join in November, and who is their manager?”

  • “Whose probation period ends before the end of the year?”

  • “How many hours did Emma Lindqvist record last week?”

  • “Which open roles have new applications this week?”

The connector

What we build for Personio

Deployed OS has no ready Personio connector yet. We build it for your company when you start, on Personio’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Employees and employments
People with the attributes your Personio admin allows, such as department, office, manager, start date and probation end.
Time off
Absence periods, such as holiday and sick leave, per person, team and date range.
Attendance
Recorded working hours and breaks per person and period.
Documents
Which documents an employee has on file, listed by category. The connector does not open their contents.
Recruiting
Open roles and their applications, from Personio’s recruiting API, which Personio still marks as beta.
Security

Who sees what

Read-only
The connector reads. It does not request or approve time off, change an employee record or upload documents.
Company API credentials, access per group
Personio’s API connects with credentials your Personio admin creates for the company, not with each person’s own Personio login. So Deployed OS decides who gets it: admins choose which groups get Personio, and a group without access never sees the connector.
Salary data kept apart
The credentials return only the fields your admin selects in Personio. We leave salary and other sensitive fields out unless you ask for them, and then only for the groups you name, such as HR or payroll.
Every call logged
Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Setup

Set up the Personio connector in three steps

01
We go through with you which questions matter most and who should be able to ask them, and decide together which Personio fields the connector may read.
02
Your Personio admin creates API credentials with read access to those areas and fields, and you choose which groups get Personio in Deployed OS.
03
People in those groups add your company’s Deployed OS connection in Claude or ChatGPT. From then on they just ask.
Compared

Personio’s own MCP server or Deployed OS?

Personio has its own MCP server, in beta and not yet open to every customer. Once an admin turns it on, each person connects with their own Personio account and it only sees what they may already see in Personio. It reads employee profiles, time off, compensation and performance reviews, and requesting time off can be turned on separately. For an HR team that wants Personio in Claude, it is a good fit.

Deployed OS is for when Personio is one system among several. It sits next to your other tools in one company connection, admins decide which groups get Personio, every call is logged in one place, and the same connection works in both Claude and ChatGPT, next to your company’s skills and guardrails.

Their documentation: Personio MCP server (beta)

Questions

Personio MCP: common questions

Yes. Personio has its own MCP server in beta, not yet open to every customer, and it works within each person’s own Personio permissions. Deployed OS adds Personio to one company connection with your other systems, with access per group, one log and the same setup in Claude and ChatGPT.

No. The connector reads employees, time off, attendance, document lists and recruiting. It does not request or approve time off, edit records or upload documents.

Nobody, unless you decide otherwise. The connector only receives the fields your Personio admin allows on the API credentials. If salary should be readable, we keep it to the groups you name, such as HR or payroll, and every call is logged.

No. Personio’s API connects with company credentials, so the connector cannot apply each person’s own Personio permissions. Access is set in Deployed OS instead: which groups get Personio, and which fields the connector may read at all.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Personio data is fetched when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.