[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# BambooHR MCP tools

> The BambooHR MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/bamboohr

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

BambooHR has 13 operations on the Cotlet MCP server, in bamboohr_read and bamboohr_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `bamboohr_read`, `bamboohr_write`
- Connects with: Your own BambooHR account; every tool follows the access level of that account
- Integration page: https://cotlet.dev/integrations/bamboohr-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`find_employee`](https://cotlet.dev/docs/mcp/bamboohr/find_employee.md) | Employees matching a name in the directory, with the employee ID the other tools need. |
| [`list_task_lists`](https://cotlet.dev/docs/mcp/bamboohr/list_task_lists.md) | Task lists and their tasks from the Onboarding or Offboarding settings. |
| [`list_onboarding_tasks`](https://cotlet.dev/docs/mcp/bamboohr/list_onboarding_tasks.md) | Onboarding tasks on an employee's Onboarding tab with list, assignee, due date and status. |
| [`list_offboarding_tasks`](https://cotlet.dev/docs/mcp/bamboohr/list_offboarding_tasks.md) | Offboarding tasks on an employee's Offboarding tab with list, assignee, due date and status. |
| [`list_signature_templates`](https://cotlet.dev/docs/mcp/bamboohr/list_signature_templates.md) | E-signature templates on the Files tab, with the folder the signed copy is saved to. |
| [`list_signature_requests`](https://cotlet.dev/docs/mcp/bamboohr/list_signature_requests.md) | Signature requests from the Signed Documents report: who has signed and who is still pending. |
| [`list_pending_time_off_requests`](https://cotlet.dev/docs/mcp/bamboohr/list_pending_time_off_requests.md) | Time off requests waiting for approval in your BambooHR inbox, or in the company inbox for admins. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`add_task_lists`](https://cotlet.dev/docs/mcp/bamboohr/add_task_lists.md) (Confirm) | Import onboarding or offboarding task lists to an employee, as Add Task List(s) and Save Tasks do. |
| [`update_employee_task`](https://cotlet.dev/docs/mcp/bamboohr/update_employee_task.md) (Confirm) | Change who a task is assigned to or when it is due, on one employee's checklist. |
| [`complete_employee_task`](https://cotlet.dev/docs/mcp/bamboohr/complete_employee_task.md) (Confirm) | Mark one onboarding or offboarding task done, or open it again. |
| [`request_signature`](https://cotlet.dev/docs/mcp/bamboohr/request_signature.md) (Confirm) | Send an e-signature template to one or more employees. |
| [`remind_signature_signers`](https://cotlet.dev/docs/mcp/bamboohr/remind_signature_signers.md) (Confirm) | Send a reminder for pending signature requests, as the Signed Documents report does. |
| [`decide_time_off_request`](https://cotlet.dev/docs/mcp/bamboohr/decide_time_off_request.md) (Confirm) | Approve or deny a time off request waiting for you. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.