Skip to content

PeopleForce MCP connector

The PeopleForce connector brings departments, divisions, locations and asset assignments into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update PeopleForce records inside their own access, with every change logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect PeopleForce to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect PeopleForce once

  1. Open Connections, choose Add connection, and pick PeopleForce.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a PeopleForce API key. One person generates a token in PeopleForce and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

peopleforce
PeopleForce
360learning
7shifts
Altera Payroll
BambooHR
Dayforce
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

PeopleForce MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

PeopleForce MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

PeopleForce MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect PeopleForce to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with PeopleForce through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • HR

    Set up a new department after a reorg

    Create the department in PeopleForce, place it under the right division, and update the records that moved, all from a single plain request instead of a dozen forms.

  • IT

    Hand a laptop to a new starter

    Record the asset assignment in PeopleForce the moment the laptop leaves the cupboard, and update it when the machine is swapped or returned.

  • Operations

    Open a new office location

    Add the location to PeopleForce and move the right departments under it without clicking through every page of the settings.

  • Finance

    Keep asset categories tidy before the audit

    List every asset category in PeopleForce, rename the ones that drifted, and remove duplicates before the auditors ask where the equipment sits.

  • People Ops

    Check which division a team sits in

    Ask for a department or division by name and get the PeopleForce record back without opening the org chart.

  • Facilities

    Close a location that has shut

    Update or remove the location in PeopleForce and tidy the asset assignments tied to it, so nothing is left pointing at an empty office.

Try asking

  • “Create a Customer Success department under the Revenue division”
  • “Which asset categories do we have in PeopleForce?”
  • “Assign laptop LT-0412 to the new hire in the Kyiv office”

See all 391 PeopleForce tools below

Compare

Elaichi vs Zapier MCP vs Composio for PeopleForce

All three can connect PeopleForce to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for PeopleForce, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over PeopleForce tools Allow or restrict single PeopleForce tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per PeopleForce call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

PeopleForce tools for your AI agents

391 tools are ready to call through Elaichi's MCP endpoint the moment you connect PeopleForce, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 275 of 391 PeopleForce tools here. Connect PeopleForce and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting PeopleForce gets you

6 screens from the product, each doing one job for your PeopleForce account.

The agent

Ask about departments and assets in plain language.

Get answers from live PeopleForce records, no menus, no exports and no waiting.

  • departments
  • divisions
  • locations
  • asset assignments

Ask Elaichi to work across your apps.

Create a Customer Success department under the Revenue division

Which asset categories do we have in PeopleForce?

Assign laptop LT-0412 to the new hire in the Kyiv office

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint connects PeopleForce to every client.

Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

391 PeopleForce tools, ready without writing code.

Departments, divisions, locations, asset assignments and asset categories, covered with no connector code.

  • Create a PeopleForce department
  • Delete a PeopleForce department by ID
  • Get single PeopleForce department by ID
  • Update a PeopleForce department by ID
ElaichiTools
Tool Action Description
Create a PeopleForce department Create Create a department in peopleforce. Returns the created department object including id, name, parent_id, manager_id, created_at, updated_at, and fields (custom fields with values). Required: name.
Delete a PeopleForce department by ID Delete Delete a department in peopleforce by id. Returns an empty 204 response on success. Required: id.
Get single PeopleForce department by ID Get Get a single peopleforce department by id. Returns: id, name, parent_id, manager_id, created_at, updated_at, fields, applicant, pipeline_state. Required: id.
Update a PeopleForce department by ID Update Update a department in peopleforce by id. Returns the updated department object including id, name, parent_id, manager_id, created_at, updated_at, and fields (custom fields with values). Required: id, name.
Create a PeopleForce location Create Create a new location in peopleforce. Returns the created location object including id, name, country_code, address, time_zone, holiday_policy_id, created_at, and updated_at. Required: name.

Toolboxes

Every team gets its own PeopleForce toolbox.

HR, IT and Finance each work from a toolbox scoped to their own job.

  • HR
  • IT
  • Finance
  • Operations
ElaichiToolboxes
Name Source template Tools Created

HR toolbox

PeopleForce · departments and divisions

PeopleForce starter 18 Mar 4, 2026

IT toolbox

PeopleForce · asset assignments

— 9 Mar 2, 2026

Finance toolbox

PeopleForce · asset categories

— 24 Feb 27, 2026

Operations toolbox

PeopleForce · locations

PeopleForce starter 6 Feb 19, 2026

People Ops toolbox

PeopleForce · org structure

— 31 Jan 30, 2026

Facilities toolbox

PeopleForce · offices and equipment

— 12 Jan 22, 2026

Shared connections

Teammates work through PeopleForce without a credential.

One person connects, shares with teams, and nobody else ever sees the API key.

  • HR
  • IT Support
  • Finance
  • Operations
ElaichiConnections
Connection Scope Status Access
PE

PeopleForce (HR)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PE

PeopleForce (IT Support)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PE

PeopleForce (Finance)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PE

PeopleForce (Operations)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PE

PeopleForce (Facilities)

Connected by Ryan Hayes

Personal • Active Not shared
PE

PeopleForce (People Ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every PeopleForce change names who made it.

When, who, what happened and which record, kept in an append-only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

PeopleForce Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

PeopleForce Departments Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

PeopleForce Departments List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts the work, a person approves.

Asset assignments are fetched, grouped and drafted into a digest before posting back to PeopleForce.

PeopleForce digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch departments

    PeopleForce

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    PeopleForce

    Queued

Collections and dashboards

PeopleForce health numbers arrive before anyone asks.

Four metrics, a 14 day chart and a team breakdown, computed without a model.

PeopleForce health

Refreshed 4 minutes ago · every 15 minutes · from the departments collection

Live

Departments

1,284 ↓ 12%

Divisions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Departments created

Last 14 days

By team

Share of activity

HR 34%

IT Support 27%

Finance 21%

Operations 18%

FAQ

Frequently asked questions

How do I connect PeopleForce to Claude?

Two steps. In Elaichi, choose PeopleForce and paste in the API key from your PeopleForce account, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and PeopleForce is ready to ask about.

Does PeopleForce work with ChatGPT and Cursor as well as Claude?

Yes. The PeopleForce connection you make in Elaichi is reached through one endpoint, https://api.elaichi.ai/mcp, and that same address works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect PeopleForce once and every client picks it up.

What can an AI agent actually do with my PeopleForce data?

It can look up a department or division in PeopleForce, create or rename one, add or change a location, and record, update or remove asset assignments and asset categories. You ask in plain words, such as create a Support department under the Customer division, and it does the work in PeopleForce. Short concrete asks work better than long sentences.

Does connecting PeopleForce give the AI everything in my account?

No. Every request to PeopleForce runs as the person who signed in, so the AI sees only the departments, locations and assets that person could already open in PeopleForce. Elaichi can narrow that further with roles and restrictions, and it never widens it.

Can my team share one PeopleForce connection?

Yes. One person connects PeopleForce in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in as themselves, so the audit log names the person who changed a department or an asset assignment, not a shared account.

Can I stop an agent from deleting or changing things in PeopleForce?

Yes. Restrictions in Elaichi work per action, so you can allow reading departments and locations in PeopleForce while blocking deletes or updates. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a PeopleForce connection when someone leaves?

Offboarding the person in Elaichi ends their access to PeopleForce at once, across every client they used. If they shared a PeopleForce connection with a team, it keeps working for everyone else. Disconnecting PeopleForce once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the PeopleForce MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. PeopleForce is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for PeopleForce?

Yes. Both let Claude, ChatGPT or Cursor use PeopleForce. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every PeopleForce call.

How is Elaichi different from Composio for PeopleForce?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to PeopleForce: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put PeopleForce in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.