Connect BambooHR to Claude Code

Make Claude update employee records and file time off in BambooHR. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect BambooHR to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect BambooHR, you add a BambooHR MCP server: a small hosted service that exposes BambooHR's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own BambooHR account. No API keys pasted into config files.

claude mcp add --transport http bamboohr https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in BambooHR once connected?

Full read-write BambooHR access lets Claude keep records current and move HR work forward: update an employee's role or compensation, file or approve a time-off request, add a new hire and kick off onboarding tasks, and pull a report, all from chat with your approval on the changes that matter.

Update an employee's job title, department, or compensation field
Add a new hire and start their onboarding task list
File a time-off request, or approve a pending one after you confirm
Adjust an employee's manager or reporting line
Generate a custom report and summarize headcount or turnover
Update contact details and emergency information on a record

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same BambooHR access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the BambooHR API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when BambooHR changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build BambooHR connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same BambooHR connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own BambooHR account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on BambooHR's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to BambooHR?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the BambooHR account it signs in with. Revoking access is one click in BambooHR.

More on the BambooHR connector

BambooHR connector for claude.ai Gusto + Claude Code Rippling + Claude Code Workday + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us