PeopleForce MCP server: connect Claude, ChatGPT or any AI assistant

Capabilities

What your assistant can answer today

Questions about who is away, how much leave is left and who works where — answered by the same queries PeopleForce runs for itself, so the answer in your assistant and the answer in PeopleForce cannot drift apart.

Who is away on a given day

Absences for any date, with public holidays included. It is the same query behind the Who's out widget on the dashboard, so the answer matches what your team already sees in PeopleForce.

How much leave someone has left

Leave types and remaining balances for a person, taken from the balances PeopleForce already calculates. Useful when a manager is planning cover and does not want to open the system to check.

Who works where, and who reports to whom

Search your people by position, department, location, manager, or any field your role can already see — custom fields included. It runs the same search as the HR directory.

The answer depends on who is asking

Every lookup runs as the person asking. For current employees, each answer is bounded by that person's own role, directory visibility and field-level restrictions. Two people asking the same question can get different answers — and should.

This is what an assistant can do over MCP right now. We keep widening it.

Setup

How the connection works

Two steps, and neither of them involves a key. An administrator opens the door for the company; each person then connects their own assistant and signs in as themselves.

Step 1

An administrator turns MCP on

Settings → Integrations → Model Context Protocol (MCP). Until this is done, nothing can connect.

The page then shows your company's server address — your PeopleForce web address followed by /mcp — with a button to copy it
It also gives a ready-made command for Claude Code, so nobody has to assemble one
Administrators can see and revoke every connection in the company from the same page

Step 2

Each person connects their assistant

In the assistant, add PeopleForce as a custom connector — a remote MCP server — using that address.

The first request opens a PeopleForce sign-in page; you sign in as yourself and approve the connection
From then on the assistant acts as you, with your permissions, until you disconnect it
Connecting this way creates no API key to paste or share — signing in is what ties the connection to you

Step-by-step: Claude and Claude Code →

Step-by-step: ChatGPT →

Mechanics

What is read, and in which direction

Every exchange happens on demand: your assistant asks a question and PeopleForce answers it. There is no sync to configure and no schedule running in the background. What the assistant receives becomes part of your conversation there, kept under that assistant's own data settings.

What is read	Direction	When	Data
People directory Structured search across your people	PeopleForce Your assistant	on each question	name, position, department, location, manager and any other field your role may see
Absences Who is away on a given day	PeopleForce Your assistant	on each question	dates, leave type, public holidays; a private leave type appears as a generic label
Leave balances Remaining days by leave type	PeopleForce Your assistant	on each question	leave type and remaining balance for a person
Field catalogue What can be returned and filtered	PeopleForce Your assistant	usually once, at the start of a conversation	field and filter names for your company — not the values behind them

Every row runs as the person who asked. Two people asking their assistants the same question can get different answers: for current employees, each answer is bounded by that person's own role, directory visibility and field-level restrictions — the same boundaries that apply when they open PeopleForce themselves.

Prefer an assistant inside PeopleForce?

AI Companion answers from the same data, and reads your knowledge base too

Request a demo

Permissions and privacy

An AI assistant is a new way into your people data, so the question is not what it can read in general — it is what it can read for the person holding it.

Your assistant looks things up as you

Every lookup runs under your own PeopleForce account. For current employees, your role, directory visibility and field-level restrictions apply just as they do in PeopleForce. If compensation is hidden from you in PeopleForce, it stays hidden here — including inside a total or a breakdown.

Private leave stays private

Absences recorded under a private leave type show a generic label, exactly as they do everywhere else in the product. Connecting an assistant does not widen what a colleague can learn about a colleague.

PeopleForce doesn't train AI models on your data

Your data is not used to train or improve any model, and a connection is bound to your company — it cannot read another company's data. What happens to a conversation afterwards follows the assistant's own settings; the Claude and ChatGPT guides spell out each one.

You can see every connection, and end it

Each person sees their connected assistants on their Preferences → Security page, under Connections, with the date they approved each one, and can revoke any of them; the assistant loses access immediately. Administrators see every connection in the company under Settings → Integrations → Model Context Protocol (MCP) → Manage connections.

Offboarding closes the door by itself

When someone is terminated in PeopleForce, their MCP connections are revoked automatically. There is no separate checklist item to forget, and no assistant left holding access after the person has gone.

Conditions, and what this is not

Where MCP sits next to the rest of PeopleForce, and what it does not claim to be.

MCP brings your assistant to PeopleForce; Companion is ours inside it

Over MCP an assistant reads your people data from wherever you work. AI Companion is the assistant built into PeopleForce: it answers from the same data and also reads your published knowledge base and draws charts in its replies. Companies use both, for different moments.

In this release, an assistant reads

An assistant answers questions; it does not submit, approve or change anything. People keep doing that in PeopleForce, where the audit trail lives. This is the current scope, and we keep widening what an assistant can do here.

It connects an AI client, not another app

MCP is the standard an AI assistant uses to reach a system. It is not a connector between PeopleForce and a messaging or project tool — those are ordinary integrations, and you will find them in the catalogue.

An administrator switches it on

MCP is off until someone with administrator access enables it under Settings → Integrations. If the page is not there, MCP hasn't been enabled for your account yet: the PeopleForce team enables it first, so talk to your account manager or our support team.

Talk to us about enabling MCP →