---
updatedAt: 2026-09-10T19:57:13.000Z
agentTools:
  projectIndex: https://documentation.bamboohr.com/llms.txt
---

# BambooHR and AI

> **Beta.** BambooHR's AI connectors are in beta. [Share feedback anytime](https://bamboohr.qualtrics.com/jfe/form/SV_bpYQdZKMVYHzBUG). It goes straight to the team building this.

Bring your BambooHR data into the AI tools your team already uses. Ask questions in plain language, pull reports, and handle routine HR tasks without leaving Claude or ChatGPT.

## How it fits together

BambooHR's AI integrations are built on an open standard called the [Model Context Protocol (MCP)](https://modelcontextprotocol.io). Think of MCP as a shared language between AI assistants and the systems that hold your data. We use it as the foundation so one secure connection can serve more than one AI tool.

* **[Claude Connector](./claude-connector)** is the most polished path and where we recommend starting. You add BambooHR to Claude, sign in once, and start asking questions.
* **[ChatGPT Connector](./chatgpt-connector)** is available to a smaller beta group. ChatGPT support is newer, so setup has an extra step and behavior varies more.
* **[MCP Server](./mcp-server)** is the foundation underneath both, and the reference for developers who want to know exactly which tools exist and how access works.

## Before you start

A BambooHR admin has to turn on the **AI Connectors** app before anyone at your company can connect. This is the switch that decides whether AI assistants can reach your BambooHR data at all.

1. In BambooHR, go to **Settings**, then **Apps**.
2. Find **AI Connectors** and enable it.
3. Under **Give access to**, choose who can connect: **admins only** (the default), **specific access levels**, or **all employees**.
4. Click **Save**.

A few things worth knowing:

* Anyone outside the audience you choose is stopped at sign-in with a message telling them what to ask their admin for.
* Disabling the app revokes every existing connection at your company. Nobody has to disconnect anything by hand.
* Narrowing the audience later removes access for the people affected, usually within an hour.

## What you can do

The exact experience depends on which AI tool you connect, but the underlying capabilities are the same:

* Look up employee details, time off balances, and reporting lines
* Search and group employees by department, location, manager, or custom field
* Run saved reports and query reporting datasets, then summarize the results
* Check who's out and what company holidays are coming up
* Review job openings and candidate pipelines
* Create and manage time off requests and goals, when your permissions allow it

## Who it's for

These integrations are built first for **HR admins**, who have the widest access and get the most out of them. They also work for **managers** and **individual contributors**, scoped to what each person can already see in BambooHR.

## Getting started

| If you want to…                                     | Start here                               |
| --------------------------------------------------- | ---------------------------------------- |
| Ask questions about your BambooHR data in Claude    | [Claude Connector](./claude-connector)   |
| Use BambooHR inside ChatGPT                         | [ChatGPT Connector](./chatgpt-connector) |
| See every available tool and how access is enforced | [MCP Server](./mcp-server)               |

## Security and access

Every request runs as you, against the same permissions BambooHR applies when you're signed in. An AI assistant cannot see or change anything you couldn't see or change yourself.

* **Sign-in happens on BambooHR.** Authentication uses OAuth, so you enter your credentials on BambooHR's own login screen and the AI tool never sees your password.
* **You approve the connection.** Before anything is shared, BambooHR shows you what the connector is being granted and you choose whether to allow it.
* **Your admin stays in control.** A BambooHR admin decides who can connect, and turning the AI Connectors app off revokes every connection immediately.
* **Access follows your access level, not your job title.** If a result looks smaller than you expected, that is almost always permissions rather than missing data.

For how access works inside each integration, see the individual pages above.

<br />