Summary
Wraps BambooHR's v1 API through a streamable HTTP transport, giving you read access to employee directories, detailed personnel records, time-off requests, and profile file metadata. You get five tools covering the basics: listing employees, fetching individual records with custom field selection, pulling the full directory with manager hierarchies, searching time-off by date range, and retrieving document lists from employee profiles. Hosted by Pipeworx as part of their multi-source gateway, so you can either connect directly to the BambooHR endpoint or tap into their broader catalog. Useful when you need HR data in Claude without building your own API client, especially for quick lookups or generating reports from personnel information.
Keeps your Mac awake while Claude Code, Codex or Cursor works. Lets it sleep when they are done.
Try free for 7 days →
Block distracting apps from your iPhone permanently without a 3rd party app. Free and open source.
Block now (100% free) →
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →
Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →mcp-bamboohr
BambooHR MCP Pack — wraps the BambooHR API v1
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
bamboohr_list_employees | List all employees with directory info. Returns IDs, names, departments, job titles, and contact details. |
bamboohr_get_employee | Get detailed employee info by ID (e.g., "12345"). Specify fields like firstName, lastName, email, department. Returns requested data. |
bamboohr_get_directory | Get complete employee directory with names, titles, departments, contact info, and manager assignments for all staff. |
bamboohr_list_timeoff | Search time-off requests by date range (e.g., "2024-01-01" to "2024-12-31"). Returns approved/pending requests with employee names and absence types. |
bamboohr_get_employee_files | Get files in an employee's profile by ID. Returns file names, upload dates, and file types. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bamboohr": {
"url": "https://gateway.pipeworx.io/bamboohr/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/bamboohr/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/bamboohr_list_employees. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"bamboohr": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-bamboohr"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-bamboohr
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bamboohr data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Featured
Keeps your Mac awake while Claude Code, Codex or Cursor works. Lets it sleep when they are done.
Try free for 7 days →Block distracting apps from your iPhone permanently without a 3rd party app. Free and open source.
Block now (100% free) →Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →