Claude

Connect Claude to your PeopleForce data

AI assistants / Switched on by an administrator

Add PeopleForce to Claude as a custom connector — on claude.ai, in Claude Desktop or in Claude Code — then sign in as yourself and ask about leave, absences and who works where. This guide takes you from the administrator's switch to your first question.

Overview

What Claude can do with PeopleForce

PeopleForce runs its own MCP server — the open standard Claude uses to reach other systems. Once connected, Claude can look up, as you:

  • Who is away on a given day, public holidays included

  • How much leave someone has left, by leave type

  • Who works where and who reports to whom, including the custom fields your role can see

Every answer comes from live PeopleForce data, looked up under your own PeopleForce account. In this release Claude reads and answers; it doesn't submit, approve or change anything.

Setup

Before you start

Three things need to be in place. The first is a one-off job for an administrator.

MCP is switched on in PeopleForce

An administrator turns it on under Settings → Integrations → Model Context Protocol (MCP). Until then, nothing can connect. If there is no MCP page, it hasn't been enabled for your account yet: the PeopleForce team enables it first — ask your account manager or our support team.

You have your company's server address

It is on the same page, with a copy button: your PeopleForce web address followed by /mcp — for example https://your-company.peopleforce.io/mcp. The address decides which company you sign in to.

Your Claude plan can add custom connectors

Custom connectors work on Claude Free, Pro, Max, Team and Enterprise. A Free account can add one. On Team and Enterprise, an Owner adds PeopleForce for the whole organisation first.

Claude on the web and desktop

Connect PeopleForce in Claude

The same steps work on claude.ai and in Claude Desktop. Once you are connected, PeopleForce is also there the next time you sign in to Claude on iOS or Android.

Step 1: Add PeopleForce as a custom connector

Go to Customize → Connectors, click + and choose Add custom connector. Paste your company's server address and click Add. Leave Advanced settings empty. PeopleForce registers Claude automatically, so there is no client ID or secret to copy.
Step 1: Add PeopleForce as a custom connector

Step 2: Sign in to PeopleForce and approve

When Claude connects, it opens PeopleForce's own sign-in page. Sign in as yourself — if you are already signed in, you go straight to the approval — and let Claude read your PeopleForce data under your own account. Claude then appears under Connections on your Preferences → Security page in PeopleForce.
Step 2: Sign in to PeopleForce and approve

Step 3: Switch PeopleForce on in a conversation

In a chat, click + (or type /), hover over Connectors and switch PeopleForce on. Then ask in plain language — for example, Who's out next Tuesday in the Warsaw office? or How many days of annual leave does Anna have left?
Step 3: Switch PeopleForce on in a conversation

Step 4: Choose what Claude may do without asking

In Customize → Connectors, open PeopleForce to see its four tools: Search people, List people fields, Who's out and People leave balances. Set each one to Always allow, Needs approval or Blocked. All four only read data.
Step 4: Choose what Claude may do without asking
Team and Enterprise

An Owner adds PeopleForce once, for everyone

An Owner goes to Organization settings → Connectors, clicks Add, hovers over Custom, chooses Web and pastes the server address. Everyone else then finds PeopleForce in Customize → Connectors and clicks Connect to sign in as themselves. Each person's lookups run under their own PeopleForce account, whoever added the connector.

Claude Code

Connect PeopleForce in Claude Code

Claude Code connects from your terminal. PeopleForce's MCP page has the command ready to copy, under Add to Claude Code.

claude mcp add --transport http peopleforce https://your-company.peopleforce.io/mcp

Add the server, sign in, check

Run the command above. To use PeopleForce in every project, not just this one, add --scope user before the address. In Claude Code, run /mcp and follow the steps in your browser to sign in to PeopleForce and approve. If the browser doesn't open, copy the link Claude Code shows. claude mcp list then shows PeopleForce as ✔ Connected. Claude Code refreshes the sign-in on its own, so you stay connected until you remove the server or revoke it in PeopleForce.
Add the server, sign in, check

Your data

What Claude reads, and what stays with you

Every request runs as the person who asked. Claude reads four things, on demand, when you ask: the people directory, absences, leave balances and the names of your company's fields. It can't read your knowledge base or change anything in PeopleForce.

Claude looks things up as you

For current employees, answers follow your role, directory visibility and field-level permissions, so two colleagues asking the same question can get different answers. A private leave type shows as a generic label. A salary comes back only if your role can see that person's compensation in PeopleForce.

What happens to your conversations

PeopleForce sends an answer only when Claude asks, and doesn't use your data to train AI models. In Claude, conversations follow Anthropic's own rules: on Team and Enterprise they aren't used for training by default. On Free, Pro and Max, Anthropic's Model Improvement setting decides — and, Anthropic says, it doesn't cover raw content from MCP connectors unless you copy it into the chat.

Disconnect whenever you like

Remove PeopleForce in Customize → Connectors, or revoke Claude in PeopleForce under Preferences → Security → Connections. Administrators can see and revoke every connection under Settings → Integrations → Model Context Protocol (MCP) → Manage connections, and when someone is terminated in PeopleForce, their connections are revoked automatically.

Troubleshooting

If something doesn't work

Most problems come down to the administrator's switch, the address or the account you signed in with.

What you see

What to do

There's no MCP page under Settings → Integrations

MCP hasn't been enabled for your account yet. The PeopleForce team enables it first, so ask your account manager or our support team.

Claude can't connect, or says MCP isn't enabled

Ask an administrator to switch MCP on under Settings → Integrations → Model Context Protocol (MCP), then connect again. Check that the address ends in /mcp.

The sign-in page shows another company, or you can't sign in

The address decides the workspace. Use your own company's address and sign in with your account there.

An answer leaves out people or fields

Claude looks things up as you. For current employees, a colleague or a field that is hidden from you in PeopleForce is hidden from Claude too.

Claude answers without using PeopleForce

Switch PeopleForce on for the conversation under + → Connectors, or mention PeopleForce in your question.

Claude Code shows ! Needs authentication

Run /mcp in Claude Code and finish signing in in your browser.

Frequently asked questions

What customers asked us before connecting.

Step-by-step guide in the help center

Which Claude plans can connect to PeopleForce?

Does it work in the Claude mobile app?

Do I need an API key?

Can Claude change anything in PeopleForce?

Can Claude see salaries?

Is PeopleForce data used to train AI models?

See Claude answer questions about your own people data

We will connect an assistant to a PeopleForce workspace on the call, ask it the questions your team asks you, and show what it cannot reach.