BambooHR MCP connector
Connect BambooHR to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can look up and update employees, time off, open jobs, and applicants, with every action running as the signed-in person and landing in an audit log.
-
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 BambooHR to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect BambooHR once
-
Open Connections, choose Add connection, and pick BambooHR.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a BambooHR API key. One person generates a token in BambooHR 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.
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.
BambooHR 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.
BambooHR 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 today. The plugin directory lives at chatgpt.com/plugins.
BambooHR 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.
Connect BambooHR 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 BambooHR through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
People Ops
Catch an employee record up after a change
When someone changes title, manager, or home address, ask for their BambooHR record and have the details corrected in one go instead of clicking through every field.
-
Recruiting
Move applicants through the pipeline
See who has applied to an open job, read an application, and change its status after an interview without leaving the conversation.
-
Managers
Check who is out before approving leave
Ask which team members are on time off next week and how much balance someone has left before a new request is booked.
-
Finance
Pull a headcount report for the month
Build a custom BambooHR report of employees by location and job title so budgeting starts from live numbers rather than last quarter's export.
-
IT
Set up a new starter on day one
Create the new employee in BambooHR with their start date, job, and location so account creation and equipment orders can follow.
-
Office
Find the current policy document
Look up the handbook or a specific policy in BambooHR company files, download the latest version, or file a new one once it is signed off.
Try asking
- “List time off requests awaiting approval this week.”
- “Who has the lowest time off balance in Support?”
- “Show open jobs and how many applications each has.”
Compare
Elaichi vs Zapier MCP vs Composio for BambooHR
All three can connect BambooHR 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 BambooHR tools | Allow or restrict single BambooHR 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 BambooHR 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
BambooHR tools for your AI agents
406 tools are ready to call through Elaichi's MCP endpoint the moment you connect BambooHR, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 221 of 406 BambooHR tools here. Connect BambooHR and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting BambooHR gets you
6 screens from the product, each doing one job for your BambooHR account.
The agent
Ask about employees, get real answers.
Plain language questions answered from live BambooHR employees, time off requests and jobs.
- employees
- time off requests
- jobs
- applications
Ask Elaichi to work across your apps.
List time off requests awaiting approval this week.
Who has the lowest time off balance in Support?
Show open jobs and how many applications each has.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to BambooHR over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
406 BambooHR tools ready to call.
Employees, users, time off, jobs and applications covered without writing custom code.
- List all BambooHR employees
- Get single BambooHR employee by ID
- Update a BambooHR employee by ID
- Create a BambooHR employee
Toolboxes
Every team gets its own toolbox.
Recruiting sees jobs and applications, payroll sees employees, each toolbox scoped separately.
- Recruiting
- People Ops
- Payroll
- Managers
Shared connections
Teammates use BambooHR without a credential.
One connected account, shared with named teams and members, owner stays visible.
- People Ops
- Recruiting EMEA
- Payroll
- Managers
Audit log
Every time off approval is on record.
When, who, what happened, type and resource for each BambooHR call.
- 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 runs the whole review.
Fetch time off requests, group them, draft a digest, approve, post to BambooHR.
BambooHR digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
BambooHR
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
BambooHR
Queued
Collections and dashboards
Headcount numbers arrive before you ask.
Four metrics, 14 days of new employees and a team breakdown, refreshed on schedule.
BambooHR health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Time off requests
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
People Ops 34%
Recruiting EMEA 27%
Payroll 21%
Managers 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect BambooHR to Claude?
First connect BambooHR in Elaichi, which asks for your BambooHR API key and your company subdomain, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register and no client ID or secret to generate. Once Claude is connected, it signs you in through Elaichi and BambooHR is ready to use.
Does BambooHR work with ChatGPT and Cursor as well as Claude?
Yes. BambooHR is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You do not set BambooHR up again for each one.
What can an AI agent actually do with my BambooHR data?
With BambooHR connected, an agent can look up an employee, update their record, add a new starter, check time off requests and balances, book leave, list open jobs and applicants, change an application's status, build a custom report, and find or add company files. Because BambooHR has a large catalog of actions, short concrete asks such as "show Priya's remaining vacation balance" work better than long paragraphs.
Does connecting BambooHR give the AI access to every employee record?
No. Every request runs as the person who signed in, so the agent sees only the employees, time off, and files that person's BambooHR permissions already allow. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what BambooHR grants.
Can I stop an agent from deleting or changing things in BambooHR?
Yes. Restrictions in Elaichi work per action, so you can allow reading employee records and time off balances while blocking updates, new applications, or file uploads in BambooHR. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to a BambooHR connection when someone leaves?
Offboarding a person in Elaichi ends their access to BambooHR through every client at once. A shared BambooHR connection keeps working for everyone else on the team. If you disconnect BambooHR in Elaichi, it disappears from Claude, ChatGPT, Cursor, and every other client in one step.
Does the BambooHR MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. BambooHR 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 BambooHR?
Yes. Both let Claude, ChatGPT or Cursor use BambooHR. 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 BambooHR call.
How is Elaichi different from Composio for BambooHR?
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 BambooHR: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put BambooHR in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.