BambooHR MCP integration for AI agents.
Connect AI agents to BambooHR through 4 structured actions, including get company information, get employee, and list employees. Review authentication, input…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BambooHR integration exposes
The BambooHR Agent App exposes 4 provider-backed actions for productivity and data work. Its current contract lets an authorized agent retrieve basic bamboohr company profile information for the connected tenant, retrieve one bamboohr employee by id with optional field aliases, and list bamboohr employees with optional additional field aliases and cursor paging. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BambooHR account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BambooHR capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_company_informationREADRetrieve basic BambooHR company profile information for the connected tenant.
get_employeeREADRetrieve one BambooHR employee by ID with optional field aliases.
INPUTS: employeeId / fields / onlyCurrent
list_employeesREADList BambooHR employees with optional additional field aliases and cursor paging.
INPUTS: fields / limit / after / before
list_fieldsREADList BambooHR employee fields available to the connected account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_employee
employeeIdREQUIRED- The BambooHR employee ID to retrieve.
fieldsOPTIONAL- BambooHR field aliases to request, such as firstName, lastName, jobTitle, or department.
onlyCurrentOPTIONAL- Whether to return only currently effective values for historical fields.
list_employees
fieldsOPTIONAL- BambooHR field aliases to request, such as firstName, lastName, jobTitle, or department.
limitOPTIONAL- Maximum number of employees to return in one page.
afterOPTIONAL- Cursor for the next page of employees.
beforeOPTIONAL- Cursor for the previous page of employees.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company Information
Retrieve basic BambooHR company profile information for the connected tenant. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_company_informationVerify with Get Employee
Retrieve one BambooHR employee by ID with optional field aliases. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_employeeSAFETY BOUNDARY
Operate BambooHR with explicit limits
- Authorize BambooHR with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BambooHR data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `company:info`, `employee`, and `field`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the BambooHR task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
BambooHR API key used as the Basic Auth username with x as the password. Generate it from the user menu in BambooHR under API Keys: https://documentation.bamboohr.com/docs/getting-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BambooHR.