Skip to content

HRIS

HiBob MCP connector

The HiBob connector brings employee profiles, time off requests and balances, salary and lifecycle records, and people fields into Claude, ChatGPT, Cursor and any MCP client, with each person working inside their own HiBob access.

  • How it connects. OAuth or 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 HiBob to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect HiBob once

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

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

  3. Supply your own HiBob app, then approve. HiBob needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

Add connection

Choose a connector.

hibob
HiBob
360learning
7shifts
BambooHR
Charlie
Deel
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.

Connect HiBob to 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.

Connect HiBob to 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.

Connect HiBob to 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 HiBob 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 HiBob through Elaichi

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

  • People

    Set up a new hire before day one

    Create the person in HiBob, set their start date, and send the onboarding invite from one conversation instead of clicking through three screens.

  • People

    Answer who is out this week

    Pull the time off requests for a team and see at a glance who is away, when they are back, and which policy type each absence falls under.

  • Managers

    Log a time off request for someone

    Record a request on behalf of a direct report when they call in, or remove one that was entered by mistake, without opening HiBob.

  • Finance

    Check salary records before payroll closes

    List current salaries and work details for a department and compare them against the payroll file before the run is locked.

  • IT

    Close out a leaver the same day

    Mark the person as terminated in HiBob and revoke their access so the leaver checklist is done in minutes rather than at the end of the week.

  • People

    Keep profiles current after a change

    Update a job title, manager, work email or custom people field when someone moves teams, and add a new field when the business needs to track something new.

Try asking

  • “List HiBob time off requests approved this week”
  • “Who joined HiBob with a start date next month”
  • “Show HiBob people lifecycle changes in the Berlin office”

See all 108 HiBob tools below

AI tools

HiBob tools for your AI agents

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

See it in Elaichi

What connecting HiBob gets you

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

The agent

Ask about people, get answers from HiBob.

Plain language questions return live HiBob people, time off requests and lifecycle records.

  • people
  • time off requests
  • lifecycle records
  • employment records

Ask Elaichi to work across your apps.

List HiBob time off requests approved this week

Who joined HiBob with a start date next month

Show HiBob people lifecycle changes in the Berlin office

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach HiBob.

One org MCP endpoint over OAuth, 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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

108 HiBob tools are ready to call.

People, time off requests and lifecycle methods are cataloged, with no custom code.

  • List all HiBob people
  • Get single HiBob person by ID
  • HiBob people terminate
  • Update a HiBob person by ID
ElaichiTools
Tool Action Description
List all HiBob people List Use this endpoint to retrieve employees with specified criteria in HiBob. Returns employee fields such as fullName, displayName, creationDateTime, work details (startDate, manager, department, title), avatarUrl, and about information. Supports filtering and inclusion of inactive employees.
Get single HiBob person by ID Get Retrieve employee data by id in HiBob. Returns fields like fullName, displayName, creationDateTime, work details (startDate, manager, department, title), avatarUrl, secondName, and about (hobbies, superpowers).
HiBob people terminate Action Use this endpoint to terminate an employee in your Hibob account. You must provide the employee_id to specify which employee to terminate, and the terminationDate is required to set the effective date of termination.
Update a HiBob person by ID Update Update specific fields in an employee record in HiBob using id. Only employee fields are supported; position fields and table updates are not allowed. Returns success status of the update.
HiBob people update email Update Use this endpoint to change an employee's email address. Use the people_id query parameter to specify the employee. If the email cannot be changed directly (e.g., for invited or active employees), an invitation will be sent to the new email address to verify and confirm the update.

Toolboxes

Every team gets its own HiBob toolbox.

Curate one toolbox per team so HR, Payroll and IT see different scopes.

  • People Ops
  • Payroll
  • Talent Acquisition
  • IT
ElaichiToolboxes
Name Source template Tools Created

People Ops toolbox

HiBob · people records and lifecycle

HiBob starter 18 Mar 4, 2026

Payroll toolbox

HiBob · employment and compensation fields

9 Mar 2, 2026

Talent Acquisition toolbox

HiBob · new hires and start dates

24 Feb 27, 2026

IT toolbox

HiBob · invites and access revocation

HiBob starter 6 Feb 19, 2026

Managers toolbox

HiBob · team time off requests

31 Jan 30, 2026

Finance toolbox

HiBob · headcount and cost centers

12 Jan 22, 2026

Shared connections

Teammates use HiBob without holding credentials.

Each connection shows who connected it and which teams and members share it.

  • People Ops
  • Payroll EMEA
  • Talent Acquisition
  • IT Onboarding
ElaichiConnections
Connection Scope Status Access
HI

HiBob (People Ops)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
HI

HiBob (Payroll EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
HI

HiBob (Talent Acquisition)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
HI

HiBob (IT Onboarding)

Connected by Daniel Ortega

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

HiBob (Managers)

Connected by Clara Nowak

Personal • Active Not shared
HI

HiBob (Finance)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every HiBob call is on the record.

When, who, what happened, type and resource, appended for each person and request.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

HiBob Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

HiBob People Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

HiBob People 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 drafts your HiBob time off digest.

Six steps fetch requests, group them, draft a digest, await approval, post back.

HiBob digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch people

    HiBob

    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

    HiBob

    Queued

Collections and dashboards

HiBob headcount numbers arrive without being asked.

Four metrics, 14 days of new people records and a team breakdown, refreshed hourly.

HiBob health

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

Live

People

1,284 ↓ 12%

Time off requests

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

People created

Last 14 days

By team

Share of activity

People Ops 34%

Payroll EMEA 27%

Talent Acquisition 21%

IT Onboarding 18%

FAQ

Frequently asked questions

How do I connect HiBob to Claude?

Connect HiBob in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. HiBob asks you to register an OAuth application inside your own HiBob account, so one person brings that client ID and secret to Elaichi once, or uses a HiBob API key if you prefer. After that nobody on the team handles a credential again, they simply sign in to HiBob as themselves when prompted.

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

Yes. Once HiBob is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect HiBob once and every client picks it up.

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

With HiBob connected, an agent can look up a person and their work, salary and lifecycle details, create a new employee and set their start date, send an onboarding invite, update a profile or work email, and terminate or revoke access when someone leaves. It can also list, create and remove time off requests, check time off balances and policy types, and add or edit people fields. Short, concrete asks such as "show me who is on leave in Support next week" work better than long paragraphs.

Does connecting HiBob give the AI access to everyone's salary and personal details?

No. Every call to HiBob runs as the person who signed in, so an agent sees exactly the employees, salaries and time off records that person could already see in HiBob and nothing more. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what HiBob itself allows.

Can my team share one HiBob connection?

Yes. One person connects HiBob in Elaichi and shares the connection with a team, and nobody else ever sees the client secret or API key. Each teammate still signs in to HiBob as themselves, so the audit log records who looked up a salary or approved a time off request, not a shared account.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading people and time off records in HiBob while blocking termination, access revocation, profile updates or deleting time off requests. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

What happens to a HiBob connection when someone leaves?

When a person is offboarded in Elaichi, their access to HiBob through every client ends immediately. If they connected HiBob and shared it, the connection keeps working for everyone else on the team. Disconnecting HiBob once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put HiBob in front of your team

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