How to integrate Bamboohr MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Bamboohr logo
Claude Code logo
divider

Introduction

Manage your Bamboohr directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Bamboohr with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Bamboohr to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Create Candidate ApplicationTool to create a candidate application.
Create Job OpeningTool to create a new job opening in BambooHR ATS.
List Job ApplicationsTool to list job applications with optional filters.
Get Benefit CoveragesTool to retrieve standard benefit coverage options.
Get Member Benefit EventsTool to list member benefit events.
Get Company EINsTool to retrieve company Employer Identification Numbers (EINs).
Get Company InformationTool to retrieve company information.
Create File CategoryTool to create new company file categories.
Create Time Off RequestTool to submit a new time off request.
List DatasetsTool to list available datasets via the Datasets API.
Create Employee DependentTool to add a dependent to an employee.
Get All Employee DependentsTool to retrieve all employee dependents.
Create EmployeeTool to create a new employee record.
Create Employee File CategoryTool to create new employee file categories.
Get Changed EmployeesTool to get employees inserted, updated, or deleted since a given timestamp.
List Company FilesTool to list company file categories and their files.
Upload Company FileTool to upload a new company file.
Get All EmployeesRetrieves all employees from the BambooHR employee directory including their basic information and status.
Get Applicant StatusesTool to retrieve applicant statuses.
Get Custom Employee FieldsTool to fetch custom employee field values.
Run Custom ReportTool to run a custom report by ID or ad-hoc fields.
Get EmployeeTool to retrieve detailed information for a specific employee.
Get Employee PhotoTool to retrieve an employee's profile photo by size.
Get Hiring LeadsTool to retrieve potential hiring leads (employees who can manage job openings) for use in creating a new job opening.
Get Job SummariesTool to retrieve a list of ATS job summaries.
Get Departments MetadataTool to list department metadata.
Get Meta DivisionsTool to list all division metadata.
List Employment Status MetadataTool to list all employment status metadata.
Get Meta Job TitlesTool to retrieve job title metadata.
Get Meta LocationsTool to list location metadata.
Get Time-Off Types MetadataTool to list time-off type metadata.
Get ReportTool to fetch a built-in or published report in JSON or other formats.
Get Time-Off BalancesTool to retrieve time-off balances for employees.
Get Time-Off RequestsTool to list time-off requests within a date range.
List Company ReportsTool to list all available company and custom reports.
Get Country OptionsTool to retrieve all available country options.
Get List Field DetailsTool to get details for all list fields.
Get Tabular Fields MetadataTool to list tabular table fields metadata.
Get UsersTool to list active users with basic info.
Update EmployeeTool to update fields on a specified employee record.
Update Time Off RequestTool to update the status of an existing time-off request.

What is the Bamboohr MCP server, and what's possible with it?

The BambooHR MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your BambooHR account. It provides structured and secure access to your HR data, so your agent can perform actions like managing employee benefits, updating payroll records, tracking time, and assisting with applicant management on your behalf.

  • Employee benefits administration: Automatically enroll employees in benefit groups, create or update benefit records, and manage company-wide benefit offerings with ease.
  • Payroll and direct deposit management: Enable your agent to create paystubs, add unpaid pay periods, and update employee direct deposit information for seamless payroll processing.
  • Dependent and tax record updates: Empower your agent to add employee dependents and modify withholding details, keeping employee records accurate and compliant.
  • Time tracking automation: Let your agent log new time tracking records for employees, ensuring precise attendance and overtime data for reporting and payroll.
  • Applicant and recruitment collaboration: Allow your agent to post comments on applicant records, streamlining feedback and communication during the hiring process.

Connecting Bamboohr via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Bamboohr) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Bamboohr account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["bamboohr"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http bamboohr-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Bamboohr. This URL will be used to connect Claude Code to Bamboohr.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Bamboohr
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Bamboohr MCP to Claude Code

bash
claude mcp add --transport http bamboohr-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (bamboohr-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Bamboohr MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your bamboohr-composio entry in the list
  • This confirms that Claude Code can now access Bamboohr tools

If everything is wired up, you should see your bamboohr-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Bamboohr

The first time you try to use Bamboohr tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Bamboohr
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Bamboohr authorization flow
  • Return to the terminal and start using Bamboohr through Claude Code

Once authenticated, you can ask Claude Code to perform Bamboohr operations in natural language. For example:

  • "Add new dependent for employee John Doe"
  • "Update direct deposit details for Sarah Smith"
  • "Log overtime hours for marketing team members"

Complete Code

Here's the complete code to get you started with Bamboohr and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["bamboohr"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http bamboohr-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Bamboohr with Claude Code using Composio's MCP server. Now you can interact with Bamboohr directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Bamboohr operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Bamboohr operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Bamboohr MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Bamboohr MCP?

With a standalone Bamboohr MCP server, the agents and LLMs can only access a fixed set of Bamboohr tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bamboohr and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Bamboohr tools.

Can I manage the permissions and scopes for Bamboohr while using Tool Router?

Yes, absolutely. You can configure which Bamboohr scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Bamboohr data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.