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.
In Elaichi
Connect HiBob once
-
Open Connections, choose Add connection, and pick HiBob.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
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
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch people
HiBob
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.