MCP connectorsPayFit

PayFit MCP: connect PayFit to Claude and ChatGPT

Ask Claude or ChatGPT who is on congés payés next week, which fixed-term contracts end before December or who has joined the Lyon office this quarter. The answer comes straight from PayFit, without an export or a message to the payroll team.

We build the connector for your company on PayFit’s own API. It only reads, it gets only the scopes your PayFit admin grants, and your company decides which groups get it. Payroll data is the most sensitive data you hold, so payslips and salaries stay out unless you choose otherwise.

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

In practice

What your team can do with PayFit in Claude and ChatGPT

HR and the DRH

Headcount questions without an export

Who works where, who has joined or left, which contracts are permanent and which are fixed-term, asked in plain words instead of pulled into a spreadsheet.

Managers

Who is off this week

Approved absences for your team, such as paid leave, RTT and sick leave, so you can plan the week before the Monday meeting.

Operations

Staffing in one view

Absences per team and period next to who is on which contract, ready for a staffing plan or the summer holiday rota.

Payroll, if you choose

Payslips for the people who already see them

Which payslips exist for an employee and period, only for the group you name, such as payroll, and only if you ask for it.

Examples

Ask it like this

“Who in the Lyon office is on congés payés next week?”
“Which fixed-term contracts end before 31 December?”
“How many people joined the company this quarter, and in which teams?”
“How many days of sick leave has the Nantes warehouse team had since September?”
“Who reports to Camille Moreau, and who is off in that team this week?”
“Which absences are still waiting for approval?”

The connector

What we build for PayFit

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

Employees: The people in your PayFit company, with the details your admin allows, such as team, manager and start date.
Contracts: Each employee’s contracts as PayFit holds them, such as contract type and start and end dates.
Absences: Absences per person, team and date range, such as paid leave, RTT and sick leave, with their status.
Payslips, only on request: Which payslips exist per employee and period. Left out by default; added only if you ask, and then only for the groups you name.

Security

Who sees what

Read-only: The connector reads. It does not add or approve absences, change a contract or employee record, or touch a payroll run.
Company API key, access per group: PayFit’s API connects with a key your PayFit admin creates for the company, not with each person’s own PayFit login. So Deployed OS decides who gets it: admins choose which groups get PayFit, and a group without access never sees the connector.
Payslips and salaries stay out: Your admin picks the scopes when creating the key, and payslips are a scope of their own. We do not ask for it unless you decide to, and then only the groups you name, such as payroll, can read them.
Every call logged: Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.

Setup

Set up the PayFit connector in three steps

We go through with you which questions matter most and who should be able to ask them, and decide together which PayFit scopes the connector needs.

Your PayFit admin creates an API key with read scopes for those areas only, and you choose which groups get PayFit in Deployed OS.

People in those groups add your company’s Deployed OS connection in Claude or ChatGPT. From then on they just ask.

Questions

PayFit MCP: common questions

Not as far as we know. PayFit has its own assistant, PayFit AI, inside PayFit, and a documented API. A few third parties offer PayFit MCP servers. We build the connector on PayFit’s API, so the answers can be used in Claude and ChatGPT next to your other systems, with access per group and a log.

No. The connector reads employees, contracts and absences. It does not add or approve absences, edit records or change anything in payroll.

Nobody, unless you decide otherwise. Payslips are a separate scope on the PayFit API key, and we leave it out by default. If payroll should be able to ask about them, we keep it to the groups you name, and every call is logged.

No. A company’s own PayFit API connection uses an API key, so the connector cannot apply each person’s own PayFit permissions. Access is set in Deployed OS instead: which groups get PayFit, and which scopes the key has at all.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. PayFit 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.