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, Microsoft Copilot and any MCP client, with each person working inside their own HiBob access.
- OAuth or API key
- Free 14-day trial
- No credit card
List HiBob time off requests approved this week
Working in HiBob with Elaichi
-
List all HiBob people
-
Get single HiBob person by ID
-
List all HiBob time off requests
How to connect HiBob to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
HiBob MCP connector for 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.
HiBob MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
HiBob MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
HiBob MCP connector for 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.
HiBob MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with HiBob through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in HiBob is logged.
-
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”
What connecting HiBob gets you
6 screens from Elaichi, each doing one job for your HiBob account.
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, Cursor or Microsoft Copilot
The agent
Ask about people, get answers from HiBob.
Plain language questions return live HiBob people, time off requests and lifecycle records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach HiBob.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
108 HiBob tools are ready to call.
People, time off requests and lifecycle methods are cataloged, with no custom code.
Toolboxes
Every team gets its own HiBob toolbox.
Curate one toolbox per team so HR, Payroll and IT see different scopes.
Shared connections
Teammates use HiBob without holding credentials.
Each connection shows who connected it and which teams and members share it.
Audit log
Every HiBob call is on the record.
When, who, what happened, type and resource, appended for each person and request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
HiBob digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
HiBob
Queued
Automations
A schedule drafts your HiBob time off digest.
Six steps fetch requests, group them, draft a digest, await approval, post back.
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%
Collections and dashboards
HiBob headcount numbers arrive without being asked.
Four metrics, 14 days of new people records and a team breakdown, refreshed hourly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for HiBob
All three can connect HiBob to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 HiBob tools | Allow or restrict single HiBob 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 HiBob 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting termination, access revocation, profile updates or deleting time off requests. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the HiBob MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. HiBob 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, Microsoft Copilot, 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 HiBob?
Yes. Both let Claude, ChatGPT or Cursor use HiBob. 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 HiBob call.
How is Elaichi different from Composio for HiBob?
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 HiBob: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put HiBob in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot