com.mcparmory/bamboohr
OCI · GHCR.IO/MCPARMORY/BAMBOOHR:1.0.6 · 2 COMPONENTS · SCANNED SEP 20
Manage employee records, time off, benefits, and payroll data
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 22186 tokens (~150/item across 147 items; 147 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 147 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/bamboohr MCP server?
com.mcparmory/bamboohr runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/bamboohr:1.0.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/bamboohr:1.0.6
claude mcp add com-mcparmory-bamboohr -- docker run --rm -i ghcr.io/mcparmory/bamboohr:1.0.6
{
"mcpServers": {
"com-mcparmory-bamboohr": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bamboohr:1.0.6"
]
}
}
} {
"servers": {
"com-mcparmory-bamboohr": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bamboohr:1.0.6"
]
}
}
} codex mcp add com-mcparmory-bamboohr -- docker run --rm -i ghcr.io/mcparmory/bamboohr:1.0.6
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-bamboohr": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bamboohr:1.0.6"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-bamboohr:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/bamboohr:1.0.6"] {
"McpServers": {
"com-mcparmory-bamboohr": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bamboohr:1.0.6"
]
}
}
} {
"mcpServers": {
"com-mcparmory-bamboohr": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bamboohr:1.0.6"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/bamboohr:1.0.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_jobs List Jobs ~163
Retrieves a list of job opening summaries from the Applicant Tracking System. Supports filtering by status group or specific status IDs, with configurable sorting. Requires ATS settings access.
| Name | Type | Req | Description |
|---|---|---|---|
| sortBy | string | – | The field by which to sort the returned job openings. Applies to the full result set before pagination. |
| sortOrder | string | – | The direction in which to sort results, either ascending or descending. |
| statusGroups | string | – | One or more status group names to filter job openings by, provided as a comma-separated string. Defaults to all non-deleted positions when omitted. |
| status_ids | string | – | One or more specific job opening status IDs to filter by, provided as a comma-separated string of integers. When combined with statusGroups, both filters are applied together. |
No output schema declared.
No examples provided.
list_list_fields List List Fields ~82
Retrieves all list fields defined in the account, including each field's ID, alias, options, manageability, and multi-value support. Archived options are included in responses to support historical data references but should not be presented as active selections.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Specifies the response format as JSON, serving as an alternative to setting the Accept header on the request. |
No output schema declared.
No examples provided.
list_member_benefit_events List Member Benefit Events ~65
Retrieves benefit enrollment events for all employees and their dependents over the past year, organized by member. Each entry identifies a member and lists their per-plan coverage events (eligibility granted, enrolled, or loss of coverage) in chronological order. Requires benefit settings access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_member_benefits List Member Benefits ~162
Retrieves a paginated list of benefit enrollment records for all members (employees and dependents) in the company for a specified calendar year, including each member's plans and enrollment status date ranges. Requires benefit admin privileges; non-admin callers receive a 403.
| Name | Type | Req | Description |
|---|---|---|---|
| calendarYear | string | yes | The four-digit calendar year for which to retrieve benefit enrollment data, in YYYY format. |
| page | string | – | The 1-based page number to retrieve; values that resolve to zero or below are rejected with a 400. Defaults to 1. |
| pageSize | string | – | The number of benefit records to return per page; must resolve to an integer between 1 and 99 inclusive, otherwise a 400 is returned. Defaults to 25. |
No output schema declared.
No examples provided.
list_tabular_fields List Tabular Fields ~67
Retrieves all tabular (table-based) fields available in the account, including each table's alias and its fields with their IDs, names, and types. Use this to discover valid table names and field metadata required for table row endpoints such as jobInfo, compensation, and employmentStatus.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_time_off_policies List Time Off Policies ~43
Retrieves all active time off policies for the company, sorted alphabetically by name. Excludes deleted policies and any policies whose associated time off type has been deleted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_time_off_requests List Time Off Requests ~322
Retrieves time off requests that overlap a specified date range, requiring both a start and end date. Results can be filtered by request ID, employee, time off type, status, or scoped to requests the caller is authorized to approve.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Scopes the response based on the caller's relationship to the requests: all viewable requests, only those the caller can approve, or only the caller's own requests. Defaults to view if omitted. |
| employeeId | integer | – | Filters the response to requests belonging to a single employee matching this ID. |
| end | string | yes | The end of the query window in YYYY-MM-DD format; requests that start on or before this date are included. Must be provided alongside the start parameter. |
| excludeNote | string | – | When set to a truthy value, the notes object is omitted from each request in the response, reducing payload size. |
| id | integer | – | Filters the response to a single time off request matching this ID. |
| start | string | yes | The beginning of the query window in YYYY-MM-DD format; requests that end on or after this date are included. Must be provided alongside the end parameter. |
| status | string | – | Comma-separated list of statuses to filter results by; accepted values are approved, denied, superceded, requested, and canceled. When omitted, requests of all statuses are returned. |
| type | string | – | Comma-separated list of time off type IDs to filter results by. When omitted, requests of all time off types are returned. |
No output schema declared.
No examples provided.
list_time_off_types List Time Off Types ~80
Retrieves all active time off types for the company, along with the company's default hours-per-day schedule. Optionally filter to only the types the authenticated employee has permission to request.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Controls filtering of returned time off types. When set to 'request', results are limited to only the types the authenticated employee has permission to request. |
No output schema declared.
No examples provided.
list_timesheet_entries List Timesheet Entries ~162
Retrieves timesheet entries (clock and hour types) for all employees or a filtered subset within a specified date range. Both dates must fall within the last 365 days and are interpreted in the company timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeIds | string | – | Comma-separated list of employee IDs used to restrict results to specific employees. When omitted, entries for all accessible employees are returned. |
| end | string | yes | The end of the date range to filter timesheet entries, inclusive. Must be a date within the last 365 days, in ISO 8601 date format. |
| start | string | yes | The start of the date range to filter timesheet entries, inclusive. Must be a date within the last 365 days, in ISO 8601 date format. |
No output schema declared.
No examples provided.
list_timezones List Timezones ~148
Retrieves a paginated list of available timezones. Supports pagination, filtering, sorting, and field projection via OData v4 query parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filters the timezone list using OData v4 filter syntax, enabling conditional expressions on timezone fields to narrow results. |
| page | integer | – | The page number to retrieve within the paginated result set, starting at page 1. |
| pageSize | integer | – | The number of timezone records to return per page. Controls the size of each paginated response. |
| sort | string | – | Specifies the sort order of results using OData v4 syntax, allowing ordering by one or more timezone fields in ascending or descending direction. |
No output schema declared.
No examples provided.
list_training_categories List Training Categories ~48
Retrieves all training categories defined for the company, returned as an object keyed by category ID with each entry containing the category ID and name. Requires the API key owner to have access to training settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_training_types List Training Types ~75
Retrieves all training types configured for the company, returned as an object keyed by training type ID. Each entry includes the training name, renewable status, renewal frequency, required status, new hire due-date window, category, link URL, description, and self-completion permission. Requires the API key owner to have access to training settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_users List Users ~108
Retrieves all users for the company, with each record including user ID, employee ID, name, email, account status, and last login time. Support admin accounts are always excluded; results can be filtered by status and returned as JSON or XML based on the Accept header.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Comma-separated list of account statuses to filter results by; only users matching at least one of the provided statuses are returned. Omitting this parameter or providing no recognized values return… |
No output schema declared.
No examples provided.
list_webhook_logs List Webhook Logs ~130
Retrieves recent delivery log entries for a specific webhook, covering the last 14 days and up to 200 entries. Each entry includes the webhook URL, last attempt and success timestamps (UTC datetime or status string), HTTP response code, payload format, and employee IDs in the payload. Note: when the rate limit is exceeded the server returns HTTP 200 with an error object instead of the log array — callers must check for an `error.code` of 429 in the response body before processing results.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The unique numeric identifier of the webhook whose delivery logs should be retrieved. |
No output schema declared.
No examples provided.
list_webhook_monitor_fields List Webhook Monitor Fields ~55
Retrieves all employee fields available for webhook monitoring, including each field's numeric ID, human-readable name, and alias. Use the returned field IDs or aliases when specifying the `monitorFields` array during webhook creation or updates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhook_post_fields List Webhook Post Fields ~57
Retrieves all available employee fields that can be included in a webhook post body, along with their related table and page record references. Use the returned field IDs or aliases in the `postFields` map when creating or updating a webhook.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~61
Retrieves all webhooks associated with the authenticated API key, returning an empty array if none exist. Each result includes the webhook ID, name, URL, creation datetime, and last fired datetime; use get_webhook to fetch full configuration details for a specific webhook.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_whos_out List Who's Out ~163
Returns a date-sorted list of employees who are out and company holidays for a specified date range. Includes both time off entries and holidays, each identified by type, defaulting to today through the next 14 days when no dates are provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | The last day of the date range to query, in YYYY-MM-DD format. Defaults to 14 days after the start date when omitted. |
| filter | string | – | Controls visibility filtering on the results. Set to 'off' to bypass the Who's Out visibility filter and return the full unfiltered feed; omitting this parameter leaves filtering enabled. |
| start | string | – | The first day of the date range to query, in YYYY-MM-DD format. Defaults to today when omitted. |
No output schema declared.
No examples provided.
query_dataset Query Dataset ~497
Retrieve paginated records from a specified dataset by providing a list of fields to return, with optional filtering, sorting, grouping, and aggregation. Use GET /api/v1/datasets/{datasetName}/fields to discover available field names before calling this endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregations | array | – | One or more aggregation operations to apply to the result set, each specifying a field and an aggregation function. Supported functions vary by field type: text/bool/options/govIdText support count;… |
| datasetName | string | yes | The unique name of the dataset to query. Use GET /api/v1/datasets to discover available dataset names. |
| fields | array | yes | The list of field names to include in the response. Use GET /api/v1/datasets/{datasetName}/fields to discover valid field names for the target dataset. |
| filters | array | – | An array of filter conditions to apply to the query. Each filter references a field, an operator, and a value; the filtered field does not need to be included in the fields list. Supported operators… |
| groupBy | array | – | An array containing a single field name by which to group results. Only one field is supported for grouping at a time. |
| match | string | – | A full-text search string used to match records across the dataset. |
| page | integer | – | The page number to retrieve when paginating through results. Must be 1 or greater; defaults to 1. |
| page_size | integer | – | The number of records to return per page. Must be between 1 and 1000; defaults to 500. |
| showHistory | array | – | An array of entity names corresponding to historical table fields whose full history should be included in the response. Use the entity name values returned by GET /api/v1/datasets/{datasetName}/fiel… |
| sortBy | array | – | An ordered array of sort directives, each specifying a field name and direction. Sort priority follows the order of items in the array, with the first item having the highest priority. |
No output schema declared.
No examples provided.
reopen_goal Reopen Goal ~77
Reopens a previously closed goal for the specified employee, returning it to in-progress status. Returns the updated goal object reflecting the new status.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeId | string | yes | The unique identifier of the employee whose goal is being reopened. |
| goalId | string | yes | The unique identifier of the closed goal to be reopened for the specified employee. |
No output schema declared.
No examples provided.
replace_break_policy Replace Break Policy ~218
Performs a full replacement of a break policy and all its associated data, including breaks and employee assignments. Any breaks or assignments not included in the request payload will be removed from the policy.
| Name | Type | Req | Description |
|---|---|---|---|
| allEmployeesAssigned | boolean | – | When set to true, this policy applies to all employees in the organization, superseding individual employee assignments. |
| breaks | array | – | Complete list of break definitions to associate with this policy; any breaks previously on the policy that are omitted here will be deleted. Each item should represent a full break configuration. |
| description | string | – | Optional human-readable description providing additional context about the break policy's purpose or compliance scope. |
| employeeIds | array | – | Complete list of employee IDs to assign to this policy; any employees previously assigned who are omitted here will be unassigned. Ignored if allEmployeesAssigned is true. |
| id | string | yes | Unique identifier of the break policy to fully replace. |
| name | string | – | Display name for the break policy, typically reflecting the region or compliance context it applies to. |
No output schema declared.
No examples provided.
replace_break_policy_breaks Replace Break Policy Breaks ~121
Replaces the complete set of breaks for a specified break policy. Breaks with an ID are updated, breaks without an ID are created, and any existing breaks omitted from the request are soft-deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | The full desired collection of breaks for the policy. Each item with an ID will be updated, items without an ID will be created, and any existing breaks not included will be soft-deleted. Order is no… |
| id | string | yes | The unique identifier of the break policy whose breaks will be replaced. |
No output schema declared.
No examples provided.
set_goal_sharing Set Goal Sharing ~119
Replaces the complete list of employees a goal is shared with, overwriting any previous sharing configuration. The goal owner's employee ID must be included in the updated list.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeId | string | yes | The unique identifier of the employee who owns the goal. |
| goalId | string | yes | The unique identifier of the goal whose sharing list will be replaced. |
| sharedWithEmployeeIds | array | – | The complete, replacement list of employee IDs with whom the goal should be shared. Must include the goal owner's employee ID; order is not significant. |
No output schema declared.
No examples provided.
unassign_employees_from_break_policy Unassign Employees from Break Policy ~100
Removes specific employees from a break policy assignment without affecting the policy itself or other assigned employees. Only applicable to policies that are not configured to apply to all employees.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeIds | array | yes | List of one or more employee IDs to remove from the break policy; order is not significant and each entry should be a valid employee identifier. |
| id | string | yes | Unique identifier of the break policy from which employees will be unassigned. |
No output schema declared.
No examples provided.
update_application_status Update Application Status ~93
Updates the status of a specific applicant tracking application. The API key owner must have ATS settings access, and valid status IDs can be retrieved via the Get Applicant Statuses endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | integer | yes | The unique identifier of the application whose status will be updated. |
| status | integer | yes | The unique identifier of the status to assign to the application. Retrieve valid status IDs using the Get Applicant Statuses endpoint. |
No output schema declared.
No examples provided.
update_break Update Break ~342
Partially updates an existing time tracking break by its UUID, modifying only the fields provided in the request body. Returns the full updated break record on success.
| Name | Type | Req | Description |
|---|---|---|---|
| availabilityEndTime | string | – | The latest clock time by which the break must be started, in HH:MM 24-hour format; applicable when availabilityType is 'time_of_day'. |
| availabilityMaxHoursWorked | number | – | The maximum number of hours an employee can work before this break must be taken; applicable when availabilityType is 'hours_worked'. |
| availabilityMinHoursWorked | number | – | The minimum number of hours an employee must have worked before this break becomes available; applicable when availabilityType is 'hours_worked'. |
| availabilityStartTime | string | – | The earliest clock time at which the break may be started, in HH:MM 24-hour format; applicable when availabilityType is 'time_of_day'. |
| availabilityType | string | – | Determines when the break becomes available: 'anytime' imposes no restriction, 'hours_worked' gates availability on hours worked thresholds, and 'time_of_day' restricts the break to a specific time w… |
| duration | integer | – | The length of the break in whole minutes. |
| id | string | yes | The unique identifier of the break to update. |
| name | string | – | Human-readable label for the break, used to identify it in schedules and reports. |
| paid | boolean | – | Indicates whether employees are compensated during this break; true means the break counts toward paid work time. |
| policyId | string | – | The UUID of the break policy this break belongs to, linking it to a set of organizational rules. |
No output schema declared.
No examples provided.
update_break_policy Update Break Policy ~129
Partially updates an existing break policy by its UUID, modifying only the fields provided in the request body. Returns the full updated break policy on success.
| Name | Type | Req | Description |
|---|---|---|---|
| allEmployeesAssigned | boolean | – | When set to true, this break policy is automatically assigned to all employees rather than a specific subset. |
| description | string | – | An optional human-readable description providing additional context about the break policy's purpose or scope. |
| id | string | yes | The unique identifier of the break policy to update. |
| name | string | – | The display name for the break policy, typically reflecting a geographic region or compliance context. |
No output schema declared.
No examples provided.
update_company_file Update Company File ~132
Updates metadata for an existing company file, including its display name, category, and employee visibility. Only fields included in the request body are modified; omitted fields remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryId | string | – | The identifier of the category (file section) to move the file into. |
| fileId | integer | yes | The unique identifier of the company file to update. |
| name | string | – | The new display name to assign to the file. |
| shareWithEmployee | string | – | Controls whether the file is visible and accessible to employees; set to 'yes' to share or 'no' to restrict access. |
No output schema declared.
No examples provided.
update_dependent Update Dependent ~467
Fully replaces an existing employee dependent record with the provided data. This is a full-replacement operation — all fields must be supplied, as omitted fields will be cleared rather than preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| addressLine1 | string | – | The first line of the dependent's street address. |
| addressLine2 | string | – | The second line of the dependent's street address, such as an apartment or suite number. |
| city | string | – | The city component of the dependent's address. |
| country | string | – | The dependent's country, provided as an ISO 3166-1 alpha-2 two-letter country code. Read responses return the full country name. |
| dateOfBirth | string | – | The dependent's date of birth. Must be provided in YYYY-MM-DD format. |
| employeeId | string | yes | The ID of the employee this dependent is associated with. Must reference an existing, valid employee. |
| firstName | string | – | The dependent's first name. |
| gender | string | – | The dependent's gender. Must be a valid gender value recognized by the system. |
| homePhone | string | – | The dependent's home phone number. |
| id | integer | yes | The numeric ID of the employee dependent record to update. |
| isStudent | string | – | Indicates whether the dependent is currently enrolled as a student. Accepted values are "yes" or "no". |
| isUsCitizen | string | – | Indicates whether the dependent is a US citizen. Accepted values are "yes" or "no". |
| lastName | string | – | The dependent's last name. |
| middleName | string | – | The dependent's middle name. |
| relationship | string | – | The dependent's relationship to the employee. Must be a valid relationship type recognized by the system. |
| sin | string | – | The dependent's Social Insurance Number (Canadian equivalent of SSN), submitted as plain text and stored encrypted. Read responses return a masked value. |
| ssn | string | – | The dependent's Social Security Number, submitted as plain text and stored encrypted. Read responses return a masked value. |
| state | string | – | The dependent's state, provided as a two-letter state code. Read responses return the full state name. |
| zipCode | string | – | The dependent's ZIP or postal code. |
No output schema declared.
No examples provided.
update_employee Update Employee ~361
Update one or more fields for an existing employee by submitting a JSON object or XML document with field name/value pairs. To discover all available field names beyond those listed here, call the list_fields operation (GET /api/v1/meta/fields). Note: if the employee is on a Trax Payroll pay schedule, a comprehensive set of required payroll fields must be included in the request.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | First line of the employee's street address. |
| city | string | – | City component of the employee's address. |
| country | string | – | Country component of the employee's address. |
| department | string | – | Name of the department the employee belongs to. |
| division | string | – | Name of the division the employee belongs to. |
| firstName | string | – | Employee's legal first name. |
| hireDate | string | – | Date the employee was hired, in YYYY-MM-DD format (ISO 8601 full date). |
| homePhone | string | – | Employee's home phone number. |
| id | string | yes | Unique identifier of the employee record to update. |
| jobTitle | string | – | Employee's job title. |
| lastName | string | – | Employee's legal last name. |
| location | string | – | Name of the work location assigned to the employee. |
| mobilePhone | string | – | Employee's mobile phone number. |
| state | string | – | State or province component of the employee's address; values are normalized to standard abbreviations (e.g., full state names are converted to their two-letter code). |
| workEmail | string | – | Employee's work email address. |
| workPhone | string | – | Employee's work phone number. |
| zipcode | string | – | ZIP or postal code component of the employee's address. |
No output schema declared.
No examples provided.
update_employee_file Update Employee File ~183
Updates metadata for an existing employee file, supporting renaming, category reassignment, and toggling employee visibility. Only fields included in the request body are modified; omitted fields remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryId | integer | – | The ID of the file category (section) to move the file into. Omit this field to leave the file in its current category. |
| fileId | integer | yes | The unique identifier of the employee file to update. |
| id | integer | yes | The unique identifier of the employee whose file is being updated. |
| name | string | – | The new display name to assign to the file. Omit this field to leave the current name unchanged. |
| shareWithEmployee | string | – | Controls whether the file is visible to the employee. Accepts 'yes' to share or 'no' to hide; also accepted as 'shareWithEmployees'. |
No output schema declared.
No examples provided.
update_employee_table_row Update Employee Table Row ~258
Updates an existing row in a specified employee table by submitting one or more field name/value pairs to modify. Targets a specific row by ID within tables such as job information or compensation history.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The effective date for the row update in YYYY-MM-DD format, determining when the change takes effect. |
| department | string | – | The department value to assign to this row. |
| division | string | – | The organizational division value to assign to this row. |
| id | string | yes | The unique identifier of the employee whose table row will be updated. |
| jobTitle | string | – | The job title value to assign to this row. |
| location | string | – | The office or work location value to assign to this row. |
| reportsTo | string | – | The identifier of the manager or supervisor this employee reports to for this row. |
| rowId | string | yes | The unique identifier of the specific row within the table to be updated. |
| table | string | yes | The name of the employee table containing the row to update, such as job information or compensation tables. |
| teams | array | – | A list of team identifiers or names associated with this row; order is not significant and each item represents a single team assignment. |
No output schema declared.
No examples provided.
update_employee_table_row_v1_1 Update Employee Table Row ~300
Updates an existing row in a specified employee table, such as job information or compensation history. Submit field changes to modify the row's effective date, location, department, job title, reporting structure, or team assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The effective date for the row update in ISO 8601 full-date format (YYYY-MM-DD), determining when the change takes effect. |
| department | string | – | The department value to assign to the employee for this row, representing the employee's organizational unit. |
| division | string | – | The division value to assign to the employee for this row, representing a high-level organizational grouping. |
| id | string | yes | The unique identifier of the employee whose table row is being updated. |
| jobTitle | string | – | The job title value to assign to the employee for this row, reflecting their role or position. |
| location | string | – | The physical or organizational location value to assign to the employee for this row. |
| reportsTo | string | – | The identifier of the manager or supervisor this employee reports to for this row. |
| rowId | string | yes | The unique identifier of the specific row within the table to update. |
| table | string | yes | The name of the employee table containing the row to update, such as job information or compensation tables. |
| teams | array | – | A list of team identifiers or names associated with the employee for this row; order is not significant. |
No output schema declared.
No examples provided.
update_goal_comment Update Goal Comment ~124
Updates the text of an existing comment on a specific employee goal. The comment, goal, and employee must all be correctly associated for the update to succeed.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Unique identifier of the comment to be updated, which must belong to the specified goal. |
| employeeId | string | yes | Unique identifier of the employee whose goal contains the comment to be updated. |
| goalId | string | yes | Unique identifier of the goal associated with the specified employee that contains the comment. |
| text | string | yes | The new text content to replace the existing comment body. |
No output schema declared.
No examples provided.
update_goal_progress Update Goal Progress ~134
Updates the completion percentage of a specific employee goal, optionally recording the completion date when the goal is fully achieved.
| Name | Type | Req | Description |
|---|---|---|---|
| completionDate | string | – | The date the goal was completed in YYYY-MM-DD format. Must be provided when percentComplete is 100. |
| employeeId | integer | yes | The unique identifier of the employee whose goal progress is being updated. |
| goalId | integer | yes | The unique identifier of the goal to update for the specified employee. |
| percentComplete | integer | yes | The current completion percentage of the goal, expressed as a whole number between 0 (not started) and 100 (fully complete). |
No output schema declared.
No examples provided.
update_goal_with_milestones Update Goal with Milestones ~390
Updates an existing performance goal for a specified employee, including support for adding, modifying, or deleting milestones within the goal. Use this version (v1.1) instead of v1 when milestone management is required.
| Name | Type | Req | Description |
|---|---|---|---|
| alignsWithOptionId | integer | – | The identifier of the strategic option or objective this goal is aligned with, linking it to a broader organizational priority. |
| completionDate | string | – | The date the goal was fully completed, provided in YYYY-MM-DD format (ISO 8601 date). Required when percentComplete is set to 100. |
| deletedMilestoneIds | array | – | A list of milestone IDs to permanently remove from this goal. Order is not significant. |
| description | string | – | A detailed narrative description providing additional context or specifics about the goal. |
| dueDate | string | yes | The target completion date for the goal, provided in YYYY-MM-DD format (ISO 8601 date). |
| employeeId | integer | yes | The unique identifier of the employee who owns the goal being updated. |
| goalId | integer | yes | The unique identifier of the goal to update, scoped to the specified employee. |
| milestones | array | – | A list of milestone objects to add to this goal. Each item should represent a discrete, trackable step toward goal completion. |
| milestonesEnabled | boolean | – | When set to true, enables milestone tracking for this goal, allowing progress to be measured through individual milestones rather than a single percent-complete value. |
| percentComplete | integer | – | The current completion percentage of the goal, expressed as a whole number between 0 and 100. Required when milestones are not enabled for this goal. |
| sharedWithEmployeeIds | array | yes | The list of employee IDs who have visibility into this goal. Must include the goal owner's employee ID; order is not significant. |
| title | string | yes | The display title of the goal. |
No output schema declared.
No examples provided.
update_list_field_options Update List Field Options ~141
Create, update, or archive options for a specific list field by its ID. Omit an option's ID to create it, include an ID to update it, or set archived to yes to hide it from future use while preserving historical data.
| Name | Type | Req | Description |
|---|---|---|---|
| listFieldId | string | yes | The unique identifier of the list field whose options are being managed. |
| options | array | – | Array of option objects to create, update, or archive on the list field. To create a new option omit its ID, to update an existing option include its ID, and to archive an option include its ID with… |
No output schema declared.
No examples provided.
update_milestone_progress Update Milestone Progress ~134
Updates the completion status of a specific milestone within an employee's goal. Use this to mark a milestone as complete or incomplete as part of tracking goal progress.
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | Indicates whether the milestone has been completed. Set to true to mark the milestone as complete, or false to mark it as incomplete. |
| employeeId | string | yes | The unique identifier of the employee whose goal milestone is being updated. |
| goalId | string | yes | The unique identifier of the goal that contains the milestone to be updated. |
| milestoneId | string | yes | The unique identifier of the milestone whose progress is being updated. |
No output schema declared.
No examples provided.
update_time_entry Update Time Entry ~269
Updates an existing time tracking entry identified by its unique ID. Use this to correct hours worked or reassign the entry to a different project, task, shift differential, or holiday.
| Name | Type | Req | Description |
|---|---|---|---|
| holidayId | integer | – | The ID of the holiday to associate with this time entry, used when the hours were worked on a recognized holiday. Omit if not applicable. |
| hoursWorked | number | yes | The corrected total number of hours worked for this entry. Always provide the full intended value, not a delta — for example, if correcting from 8.0 to 6.0 hours, send 6.0. |
| projectId | integer | – | The ID of the project to associate with this time entry. Omit if the project association should remain unchanged or is not applicable. |
| shiftDifferentialId | integer | – | The ID of the shift differential to associate with this time entry, used when the entry qualifies for differential pay. Omit if not applicable. |
| taskId | integer | – | The ID of the task to associate with this time entry. Omit if the task association should remain unchanged or is not applicable. |
| timeTrackingId | string | yes | The unique identifier of the time tracking entry to update, up to 36 characters in length (e.g., a UUID). |
No output schema declared.
No examples provided.
update_time_off_request_status Update Time Off Request Status ~151
Approves, denies, or cancels an existing time off request by updating its status. Owners and admins can complete all workflow approval steps at once, while standard approvers advance only their current step.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | An optional note to attach to the status change, such as a reason for denial or approval context. |
| requestId | integer | yes | The unique identifier of the time off request whose status is being updated. |
| status | string | yes | The new status to apply to the time off request. Use 'approved' to grant the request, 'denied' or 'declined' to reject it, and 'canceled' or 'cancelled' to withdraw it. |
No output schema declared.
No examples provided.
update_training_category Update Training Category ~86
Updates the name of an existing training category identified by its ID. Requires training settings access; returns a 409 conflict if a category with the new name already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new name to assign to the training category; must be unique across all existing training categories. |
| trainingCategoryId | integer | yes | The unique numeric identifier of the training category to update. |
No output schema declared.
No examples provided.
update_training_record Update Training Record ~209
Updates an existing employee training record by its ID. The completion date is required; all other fields such as cost, instructor, hours, credits, and notes are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | The monetary cost of the training expressed as a decimal string, corresponding to the specified currency. |
| completed | string | yes | The date the training was completed, required for every update. Must follow the yyyy-mm-dd format. |
| credits | number | – | The number of credits the employee earned upon completing the training. |
| currency | string | – | The ISO 4217 three-letter currency code representing the currency of the training cost. |
| employeeTrainingRecordId | integer | yes | The unique identifier of the employee training record to update. |
| hours | number | – | The total duration of the training expressed in hours. |
| instructor | string | – | The full name of the person who delivered or facilitated the training. |
| notes | string | – | Free-text notes providing any additional context or details about the training record. |
No output schema declared.
No examples provided.
update_training_type Update Training Type ~327
Updates an existing training type by modifying only the fields provided in the request. Requires training settings access; pass an empty string or null for the category field to remove a category assignment.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEmployeesToMarkComplete | boolean | – | When enabled, allows any employee who can view this training type to mark it as complete without manager or admin intervention. |
| categoryName | string | – | The name of the category to assign to this training type. Pass an empty string or null to remove the existing category. |
| description | string | – | A detailed description of the training type, providing context or instructions for employees. |
| dueFromHireDate | integer | – | The number of days after an employee's hire date by which this training must be completed. Only applicable when the training type is marked as required. |
| frequency | integer | – | The interval in months at which this training must be renewed. Only applicable when the training type is set to renewable. |
| id | integer | – | The unique identifier of the category to assign to this training type. |
| linkUrl | string | – | An optional URL to associate with this training type, such as a link to training materials or an external resource. |
| name | string | – | The display name of the training type. |
| renewable | boolean | – | Indicates whether this training type can be renewed on a recurring basis. If set to true, a frequency value must also be provided. |
| required | boolean | – | Indicates whether completion of this training type is mandatory for employees. |
| trainingTypeId | integer | yes | The unique identifier of the training type to update. |
No output schema declared.
No examples provided.
upload_employee_file Upload Employee File ~202
Uploads a file to a specific section of an employee's document folder via multipart/form-data. Files must be under 20MB and use a supported extension; on success, the response includes a Location header pointing to the newly created file resource.
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | yes | The numeric ID of the employee file section (category) into which the file will be uploaded. |
| file | string | yes | Base64-encoded file content for upload. The binary file content to upload, submitted as part of the multipart/form-data request body. |
| fileName | string | yes | The display name assigned to the uploaded file as it will appear in the employee's document folder. |
| id | string | yes | The ID of the employee whose file folder will receive the upload. Pass 0 to target the employee associated with the API key. |
| share | string | – | Controls whether the uploaded file is shared with the employee and made visible to them. Defaults to no if omitted. |
No output schema declared.
No examples provided.
upload_employee_photo Upload Employee Photo ~175
Uploads and replaces the photo for a specified employee, updating all size variants. The image must be a square JPEG, PNG, or BMP file of at least 150×150 pixels and no larger than 20MB; employees may upload their own photo if the company has self-photo uploads enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeId | integer | yes | The unique numeric identifier of the employee whose photo is being uploaded. |
| file | string | yes | Base64-encoded file content for upload. The image file to set as the employee's photo. Must be a square image (width and height within one pixel of each other), at least 150×150 pixels, no larger tha… |
No output schema declared.
No examples provided.
upload_file Upload File ~193
Uploads a file to a specified company file category using a multipart/form-data request. Files must be under 20MB, use a supported extension, and cannot be uploaded to read-only categories or implementation categories on companies that have completed implementation.
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | yes | The numeric ID of the file category (section) into which the file will be uploaded. Read-only categories and implementation categories (for completed implementations) are not permitted. |
| file | string | yes | Base64-encoded file content for upload. The binary file content to upload. Must be under 20MB and use a supported file extension. |
| fileName | string | yes | The display name for the file as it will appear in the company file system. |
| share | string | – | Controls whether the uploaded file is shared with all employees. Accepts 'yes' to share or 'no' to keep private; defaults to 'no' if omitted. |
No output schema declared.
No examples provided.
upsert_hour_records Upsert Hour Records ~102
Bulk create or update time tracking hour records in a single request. Note that HTTP 201 may be returned even when individual records fail validation — always inspect each item's `success` flag and `response.message` for partial failures.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of hour record objects to create or update; each item should include the relevant time tracking fields. Order is not significant, but each item's result is returned individually so partial fail… |
No output schema declared.
No examples provided.
What is the com.mcparmory/bamboohr MCP server?
com.mcparmory/bamboohr is an MCP server listed in the public MCP registry as com.mcparmory/bamboohr. Manage employee records, time off, benefits, and payroll data. This page covers its container image (ghcr.io/mcparmory/bamboohr:1.0.6).
Is the com.mcparmory/bamboohr MCP server safe to use?
com.mcparmory/bamboohr scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/bamboohr MCP server expose?
com.mcparmory/bamboohr exposes 147 tools: create_project, list_break_assessments, get_break, update_break, delete_break, and 142 more. Their descriptions and schemas cost roughly 22,186 tokens of context every time the server is loaded.
Is the com.mcparmory/bamboohr MCP server still maintained?
com.mcparmory/bamboohr is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.