# BambooHR MCP connector

Connect BambooHR to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

Source: https://elaichi.ai/connectors/bamboohr/

## Facts

| | |
| --- | --- |
| Application | BambooHR |
| Category | HRIS |
| AI tools | 406 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once BambooHR is connected

- 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.

## Connect BambooHR in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick BambooHR.
2. Optionally set Share with, then press Connect.
3. 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which BambooHR tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## BambooHR MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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 Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## BambooHR MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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.

## BambooHR MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## BambooHR MCP connector for Microsoft Copilot

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

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.
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.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect BambooHR to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a BambooHR tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone.

## What teams do with BambooHR through Elaichi

### Catch an employee record up after a change

People Ops. 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.

### Move applicants through the pipeline

Recruiting. See who has applied to an open job, read an application, and change its status after an interview without leaving the conversation.

### Check who is out before approving leave

Managers. Ask which team members are on time off next week and how much balance someone has left before a new request is booked.

### Pull a headcount report for the month

Finance. Build a custom BambooHR report of employees by location and job title so budgeting starts from live numbers rather than last quarter's export.

### Set up a new starter on day one

IT. Create the new employee in BambooHR with their start date, job, and location so account creation and equipment orders can follow.

### Find the current policy document

Office. 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.

## 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. Endpoint: 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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, Microsoft Copilot, 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 my team share one BambooHR connection?

Yes. One person connects BambooHR in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the individual behind every BambooHR action.

### 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 restricting updates, new applications, or file uploads in BambooHR. 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 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, Microsoft Copilot, 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, 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 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.

## All 406 BambooHR tools

Every tool below is callable through https://api.elaichi.ai/mcp once BambooHR is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all BambooHR employees** (List). Get employee directory for companyDomain in BambooHR. Returns employee id, displayName, firstName, lastName, gender, jobTitle, workPhone, workPhoneExtension, skypeUsername, and facebook fields. Note: Directory feature may be disabled by company.
- **Get single BambooHR employee by ID** (Get). Get employee data by specifying id and fields in BambooHR. Returns id, firstName, lastName, and other requested fields. 
- **Update a BambooHR employee by ID** (Update). Update an employee by id in BambooHR. Requires company_domain and id. Returns success message on update. If employee syncs with Trax Payroll, all specified fields must be included for successful update.
- **Create a BambooHR employee** (Create). Add a new employee in BambooHR with required fields firstName and lastName. Returns the Location header containing the URL with the new employee's id.
- **Delete a BambooHR employee by ID** (Delete). Permanently delete an employee and all associated data in BambooHR by id. Returns an empty 204 response on success. Required: id (the internal employee ID — do not pass the editable employeeNumber, which may fail with 404 or target the wrong employee).
- **List all BambooHR users** (List). Get a list of users for the companyDomain in BambooHR. Returns user id, employeeId if linked, firstName, lastName, email, status, and lastLogin in ISO 8601 format.
- **List all BambooHR time off requests** (List). Get time off requests for companyDomain with required start and end dates. Returns id, employeeId, name, status (lastChanged, lastChangedByUserId, status), start, end, created, type (id, name, icon), amount (unit, amount), notes, and dates if available in BambooHR.
- **Create a BambooHR time off request** (Create). Create a time off request for employee with id in BambooHR. Requires company_domain and employee id. Returns empty response with 201 status on success. Request includes status, start, end, timeOffTypeId, amount, notes, dates, and previousRequest.
- **List all BambooHR time off balance** (List). Get estimated future time off balances for employee id in BambooHR with required company_domain and end date. Returns timeOffType, name, units, balance, policyType, usedYearToDate, and end date fields.
- **List all BambooHR jobs** (List). Get a list of job summaries in BambooHR for the specified companyDomain. Returns job details including title, lead, created date, and status.
- **Create a BambooHR job** (Create). Add a new job opening in BambooHR with required parameters company_domain, postingTitle, jobStatus, hiringLead, employmentType, and jobDescription. Returns success status on creation.
- **Get single BambooHR job by ID** (Get). Retrieves detailed information about a specific job posting in BambooHR based on the unique job ID.
- **List all BambooHR applications** (List). Get a list of applications for companyDomain in BambooHR. Returns application id, appliedDate, status with rating, applicant info, and job info. Requires companyDomain.
- **Get single BambooHR application by ID** (Get). Get details about a specific application in BambooHR. Requires company_domain and id. Returns fields such as id, appliedDate, status, rating, education, resumeFileId, coverLetterFileId, applicant details, job details, and related counts.
- **BambooHR applications change status** (Action). Change applicant's status by application id in BambooHR. Requires companyDomain and applicationId. Returns success status on update.
- **Create a BambooHR application** (Create). Add a new candidate application to a job opening in BambooHR. Requires company_domain and jobId. Returns success status on completion.
- **List all BambooHR statuses** (List). Get a list of statuses for a company in BambooHR using company_domain. Returns all available status entries for applicant tracking.
- **List all BambooHR company locations** (List). Get company locations using company_domain in BambooHR. Returns an array of location objects for creating new job openings.
- **List all BambooHR fields** (List). Get a list of fields available in a BambooHR account using companyDomain. Returns id, name, type, and alias for each field.
- **Update a BambooHR field by ID** (Update). Use this endpoint to update one or more metadata fields in the account.  
- **Create a BambooHR custom report** (Create). Request a custom report in BambooHR with companyDomain and format. Returns the report with specified fields such as firstName and lastName. Supports filtering by lastChanged date to include only employees changed since that time.
- **List all BambooHR company files** (List). List company files and categories for companyDomain in BambooHR. Returns categories with id and name, and files with id, name, originalFileName, size, dateCreated, createdBy, and shareWithEmployee fields.
- **BambooHR company files download** (Download). Use this endpoint to download a specific file stored in the company's BambooHR file repository by providing the file_id.
- **Get single BambooHR company file by ID** (Get). Get company file by id in BambooHR using company_domain and id. Returns the file content if found.
- **Create a BambooHR company file** (Create). Add a new company file category in BambooHR using company_domain. Returns 201 status on successful creation.
- **Update a BambooHR company file by ID** (Update). Update a company file in BambooHR using company_domain and id. Returns status 200 if the file is updated. Fields updated can include name, categoryId, and shareWithEmployees.
- **Delete a BambooHR company file by ID** (Delete). Delete a company file by id in BambooHR. Requires company_domain and id. Returns 200 on successful deletion, 403 if permission denied, and 404 if file not found.
- **List all BambooHR employee files** (List). List employee files and categories for employee with id in BambooHR. Returns categories with id and name, and files with id, name, originalFileName, size, dateCreated, createdBy, and shareWithEmployee fields.
- **Get single BambooHR employee file by ID** (Get). Get an employee file by id and file_id in BambooHR. Returns the file content if found. Requires company_domain, id, and file_id.
- **Create a BambooHR employee file** (Create). Add an employee file category in BambooHR using company_domain. Returns 201 status on successful creation.
- **Update a BambooHR employee file by ID** (Update). Update an employee file by id in BambooHR with parameters name, categoryId, and shareWithEmployee. Returns status 200 if the file was updated successfully.
- **Delete a BambooHR employee file by ID** (Delete). Delete an employee file by employee id and fileId in BambooHR. Returns confirmation of deletion.
- **List all BambooHR payroll deductions** (List). Use this endpoint to retrieve a list of payroll deductions assigned to a specific employee, identified by their employee_id
- **List all BambooHR time off types** (List). Get a list of time off types for companyDomain in BambooHR. Returns id, name, units, color, and icon for each time off type.
- **List all BambooHR time off policies** (List). Get a list of time off policies for the companyDomain in BambooHR. Returns id, timeOffTypeId, name, effectiveDate, and type for each policy.
- **List all BambooHR employee time off policies** (List). List time off policies for an employee in BambooHR. Requires company_domain and id. Returns timeOffPolicyId, timeOffTypeId, and accrualStartDate for each policy.
- **List all BambooHR timesheet** (List). Get all timesheet entries for a given period with start and end dates in BambooHR. Returns id, employeeId, type, date, start, end, timezone, hours, note, projectInfo, approvedAt, and approved fields. Data limited to last 365 days.
- **Create a BambooHR clock entry** (Create). Create a timesheet clock-in entry for an employee in BambooHR. Requires company_domain and id. Returns id, employeeId, type, date, start, end, timezone, hours, note, and projectInfo with project and task details.
- **Update a BambooHR clock entry by ID** (Update). Add or edit timesheet clock entries in BambooHR with required entries including employeeId, date, start, and end. Returns id, employeeId, type, date, start, end, timezone, hours, note, and projectInfo fields for each entry.
- **Delete a BambooHR clock entry by ID** (Delete). Delete timesheet clock entries by providing clockEntryIds in BambooHR. Returns 204 on successful deletion with no content.
- **BambooHR clock entries clock out** (Action). Create a timesheet clock-out entry for an employee in BambooHR using company_domain and id. Returns id, employeeId, type, date, start, end, timezone, hours, note, and projectInfo fields.
- **Update a BambooHR hour entry by ID** (Update). Add or edit timesheet hour entries in BambooHR. Requires companyDomain and an array of hours objects with employeeId, date, hours, note, projectId, and taskId. Returns id, employeeId, type, date, hours, note, and projectInfo with project and task details.
- **Delete a BambooHR hour entry by ID** (Delete). Delete timesheet hour entries in BambooHR using companyDomain and hourEntryIds. Returns no content on success.
- **List all BambooHR webhooks** (List). Get a list of webhooks for the user API key in BambooHR. Requires company_domain. Returns webhook id, name, created date, lastSent date, and url.
- **Get single BambooHR webhook by ID** (Get). Get webhook data for a specific webhook by id in BambooHR. Returns id, name, created timestamp, lastSent timestamp, monitorFields, postFields, url, format, frequency, limit, and includeCompanyDomain fields.
- **Create a BambooHR webhook** (Create). Create a new webhook in BambooHR with required parameters company_domain, name, monitorFields, postFields, and url. Returns webhook id, name, created timestamp, lastSent timestamp, monitorFields, postFields, url, format, frequency, limit, privateKey, and includeCompanyDomain flag.
- **Update a BambooHR webhook by ID** (Update). Update a webhook by id in BambooHR with required fields name, monitorFields, postFields, and url. Returns updated webhook id, name, created timestamp, lastSent timestamp, monitorFields, postFields, url, format, frequency, limit, and includeCompanyDomain.
- **Delete a BambooHR webhook by ID** (Delete). Delete a webhook by id for the specified companyDomain in BambooHR. Returns confirmation of deletion.
- **BambooHR webhooks logs** (Action). Get webhook logs for a specific webhook by id in BambooHR. Returns webhookId, url, lastAttempted, lastSuccess, failureCount, status, and employeeIds fields.
- **BambooHR webhooks fields** (Action). Get a list of fields that webhooks can monitor in BambooHR. Requires company_domain. Returns fields with id, name, and alias.
- ...and 356 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
