[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 API and MCP server

> Yes. BambooHR has a public REST API (API key or OAuth) and a beta MCP server at {your-subdomain}.bamboohr.com/api/mcp that an admin must switch on under Settings > Apps > AI Connectors (checked 16 Oct 2026). Both cover employees, time off, goals and hiring, and the API also moves file contents. Neither has an endpoint or tool for onboarding and offboarding task lists or for e-signature requests, and the beta MCP reads file metadata only.

HR software for small and mid-size companies: employee records, time off, onboarding and offboarding task lists, e-signatures, hiring and goals in one account.

## What is the BambooHR API?

Cotlet's BambooHR API exposes 13 endpoints for your own BambooHR account: find employee, list task lists, list onboarding tasks, list offboarding tasks, list signature templates, list signature requests, list pending time off requests, add task lists to an employee, update task assignee or due date, mark task complete, request signatures, remind signers and approve or deny time off. The find_employee endpoint returns employees matching a name in the directory, with the employee ID the other tools need. Each endpoint takes simple JSON inputs like employee_id, kind or status and works both as an operation of the bamboohr_read or bamboohr_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-21

Yes. Cotlet is a hosted MCP server and REST API for BambooHR with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does BambooHR have an official API?

Yes. BambooHR has a public REST API (API key or OAuth) and a beta MCP server at {your-subdomain}.bamboohr.com/api/mcp that an admin must switch on under Settings > Apps > AI Connectors (checked 16 Oct 2026). Both cover employees, time off, goals and hiring, and the API also moves file contents. Neither has an endpoint or tool for onboarding and offboarding task lists or for e-signature requests, and the beta MCP reads file metadata only.

| Task | BambooHR official | Cotlet |
|---|---|---|
| List an employee's onboarding and offboarding tasks | No: New hire packet endpoints return packets without tasks | Yes |
| Add task lists to an employee | No | Yes |
| Change a task due date or assignee | No | Yes |
| Mark an onboarding or offboarding task complete | No | Yes |
| Request an e-signature from employees | No | Yes |
| Send reminders for pending signatures | No | Yes |
| Approve or deny a time off request | Yes: API and beta MCP both do this, within the key owner's or user's permissions | Yes |
| Find an employee | Yes: Fields you cannot see are left out | Yes |

Sources: [BambooHR API: MCP Server (beta)](https://documentation.bamboohr.com/docs/mcp-server), [BambooHR API: Claude connector](https://documentation.bamboohr.com/docs/claude-connector), [BambooHR API: Getting started (API keys and OAuth)](https://documentation.bamboohr.com/docs/getting-started), [BambooHR API reference index](https://documentation.bamboohr.com/llms.txt)

## For AI agents

```text
Yes. BambooHR has a public REST API (API key or OAuth) and a beta MCP server at {your-subdomain}.bamboohr.com/api/mcp that an admin must switch on under Settings > Apps > AI Connectors (checked 16 Oct 2026). Both cover employees, time off, goals and hiring, and the API also moves file contents. Neither has an endpoint or tool for onboarding and offboarding task lists or for e-signature requests, and the beta MCP reads file metadata only.
Cotlet provides a hosted MCP server and REST API for BambooHR: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=bamboohr, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    bamboohr_read, bamboohr_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/bamboohr, each operation at its own route, e.g. POST /api/v1/bamboohr/tasks/{task_id}/employees/{employee_id}/task/complete
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   find_employee, list_task_lists, list_onboarding_tasks, list_offboarding_tasks, list_signature_templates, list_signature_requests, list_pending_time_off_requests, add_task_lists, update_employee_task, complete_employee_task, request_signature, remind_signature_signers, decide_time_off_request
Confirm      add_task_lists, update_employee_task, complete_employee_task, request_signature, remind_signature_signers, decide_time_off_request (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/bamboohr-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=bamboohr, requests BambooHR in the Cotlet console and creates an API key there.
2. The user signs in to BambooHR once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables BambooHR for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted BambooHR server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source BambooHR MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to BambooHR in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get BambooHR only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no BambooHR login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following BambooHR's terms; Cotlet is not affiliated with BambooHR.
```

## What can an AI agent do in BambooHR?

Cotlet is best for HR and people-ops admins who want their AI agent to start onboarding and offboarding tasks, chase e-signatures and approve time off without running or fixing a server.

- **[Start onboarding tasks for a new hire](https://cotlet.dev/integrations/bamboohr-api-mcp-server/start-onboarding-tasks.md)** (runs: daily): "Find employees in BambooHR who start in the next 7 days and have no onboarding tasks yet. Add the IT setup and Manager tasks lists, and tell me which tasks have no assignee." → `find_employee`, `list_task_lists`, `add_task_lists`, `list_onboarding_tasks`
- **Run the offboarding checklist when someone leaves** (runs: daily): "For everyone with a termination date in the next 14 days, add the Offboarding list in BambooHR, assign the equipment return task to Priya Shah and set it due on their last day." → `find_employee`, `list_task_lists`, `add_task_lists`, `update_employee_task`
- **Chase overdue onboarding tasks** (runs: weekly): "Every Monday, check onboarding tasks for people hired in the last 30 days. List the open ones that are past due by assignee, and move tasks owned by someone who left to Priya Shah." → `find_employee`, `list_onboarding_tasks`, `update_employee_task`
- **[Request e-signatures and chase pending ones](https://cotlet.dev/integrations/bamboohr-api-mcp-server/request-employee-signatures.md)** (runs: weekly): "Send the 2026 Employee Handbook signature template to everyone hired this quarter who has not signed it. Then remind everyone whose request is still pending after 3 days." → `list_signature_templates`, `list_signature_requests`, `request_signature`, `remind_signature_signers`
- **Approve time off by your own rules** (runs: daily): "Go through the time off requests waiting for me in BambooHR. Approve vacation under 3 days when nobody else on the team is out, and leave everything else for me with a one-line reason." → `list_pending_time_off_requests`, `decide_time_off_request`

## Can BambooHR automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a BambooHR connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to start onboarding tasks for a new hire, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/bamboohr/employees/find. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/bamboohr/employees/find with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to BambooHR.

### find_employee

Employees matching a name in the directory, with the employee ID the other tools need. Access: read. REST: `GET /api/v1/bamboohr/employees/find`. MCP: `bamboohr_read → find_employee`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Part of the employee name. |

Returns the employees whose name matches the query, with ID, job title, department and hire date. Fields your BambooHR account cannot see are left out, never filled in. Use employee_id from each item in the task, signature and time off tools. Returns up to 25 matches; refine the query for more.

Example response:

```json
{
  "employees": [
    {
      "employee_id": "412",
      "name": "Ana Kowal",
      "job_title": "Account Executive",
      "department": "Sales",
      "hire_date": "2026-10-19"
    }
  ]
}
```

### list_task_lists

Task lists and their tasks from the Onboarding or Offboarding settings. Access: read. REST: `GET /api/v1/bamboohr/task-lists`. MCP: `bamboohr_read → list_task_lists`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `kind` | string | yes | Which checklist: 'onboarding' or 'offboarding'. |

Returns every list from the Onboarding or Offboarding settings with its tasks, including the Miscellaneous Tasks list BambooHR keeps for tasks without a list. Each task shows its default assignee, when the filters apply and the notification timing set for it. Use list_id in add_task_lists. Reads settings only and changes nothing.

Example response:

```json
{
  "kind": "onboarding",
  "lists": [
    {
      "list_id": "tl_it_setup",
      "name": "IT setup",
      "tasks": [
        {
          "task": "Order laptop",
          "assignee": "Priya Shah",
          "notify": "on due date"
        },
        {
          "task": "Create accounts",
          "assignee": "Priya Shah",
          "notify": "a day before due date"
        }
      ]
    },
    {
      "list_id": "tl_manager",
      "name": "Manager tasks",
      "tasks": [
        {
          "task": "Schedule first-week 1:1",
          "assignee": "Hiring manager",
          "notify": "15 minutes after assigned"
        }
      ]
    },
    {
      "list_id": "tl_misc",
      "name": "Miscellaneous Tasks",
      "tasks": []
    }
  ]
}
```

### list_onboarding_tasks

Onboarding tasks on an employee's Onboarding tab with list, assignee, due date and status. Access: read. REST: `GET /api/v1/bamboohr/employees/{employee_id}/onboarding-tasks`. MCP: `bamboohr_read → list_onboarding_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee ID from find_employee. |
| `status` | string | no | 'open', 'done' or 'all'. Default: open. |

Returns the tasks on one employee's Onboarding tab, grouped by task list, open first and then by due date. Each task shows who it is assigned to, its due date and whether it is done. Returns an empty list when no tasks were added yet, which is how add_task_lists callers find new hires without tasks.

Example response:

```json
{
  "employee_id": "412",
  "tasks": [
    {
      "task_id": "ot_9012",
      "task": "Order laptop",
      "list": "IT setup",
      "assignee": "Priya Shah",
      "due_date": "2026-10-16",
      "done": false
    },
    {
      "task_id": "ot_9013",
      "task": "Create accounts",
      "list": "IT setup",
      "assignee": "Priya Shah",
      "due_date": "2026-10-18",
      "done": false
    },
    {
      "task_id": "ot_9020",
      "task": "Schedule first-week 1:1",
      "list": "Manager tasks",
      "assignee": null,
      "due_date": "2026-10-19",
      "done": false
    }
  ]
}
```

### list_offboarding_tasks

Offboarding tasks on an employee's Offboarding tab with list, assignee, due date and status. Access: read. REST: `GET /api/v1/bamboohr/employees/{employee_id}/offboarding-tasks`. MCP: `bamboohr_read → list_offboarding_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee ID from find_employee. |
| `status` | string | no | 'open', 'done' or 'all'. Default: open. |

Returns the tasks on one employee's Offboarding tab, grouped by task list, open first and then by due date. Each task shows its assignee, due date and whether it is done. Returns an empty list when offboarding was not started for that employee.

Example response:

```json
{
  "employee_id": "418",
  "tasks": [
    {
      "task_id": "ft_3301",
      "task": "Collect laptop",
      "list": "Equipment",
      "assignee": "Priya Shah",
      "due_date": "2026-10-30",
      "done": false
    },
    {
      "task_id": "ft_3302",
      "task": "Remove from payroll group",
      "list": "Finance",
      "assignee": "Lena Ortiz",
      "due_date": "2026-10-30",
      "done": true
    }
  ]
}
```

### list_signature_templates

E-signature templates on the Files tab, with the folder the signed copy is saved to. Access: read. REST: `GET /api/v1/bamboohr/signature-templates`. MCP: `bamboohr_read → list_signature_templates`.

No parameters.

Returns the signature templates on the Files tab. Each template shows its name and the folder in the employee's Documents tab where the signed copy is saved. Use template_id in request_signature. Reads only; creating or editing templates stays in BambooHR.

Example response:

```json
{
  "templates": [
    {
      "template_id": "sg_handbook_2026",
      "name": "2026 Employee Handbook",
      "signed_folder": "Signed Documents"
    },
    {
      "template_id": "sg_equipment",
      "name": "Equipment Agreement",
      "signed_folder": "Signed Documents"
    }
  ]
}
```

### list_signature_requests

Signature requests from the Signed Documents report: who has signed and who is still pending. Access: read. REST: `GET /api/v1/bamboohr/signature-requests`. MCP: `bamboohr_read → list_signature_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | 'pending', 'signed' or 'all'. Default: pending. |
| `template_id` | string | no | Only requests for this template. |
| `employee_id` | string | no | Only requests for this employee. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns requests from the Signed Documents report, newest first. Each shows the employee, the template, the date requested and the date signed, empty while pending. Filter by status, template or employee. Pages hold up to 100 requests; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "requests": [
    {
      "request_id": "sr_7701",
      "employee_id": "412",
      "employee": "Ana Kowal",
      "template": "2026 Employee Handbook",
      "requested_at": "2026-10-09",
      "signed_at": null,
      "status": "pending"
    },
    {
      "request_id": "sr_7702",
      "employee_id": "418",
      "employee": "Tom Becker",
      "template": "2026 Employee Handbook",
      "requested_at": "2026-10-09",
      "signed_at": "2026-10-10",
      "status": "signed"
    }
  ],
  "next_cursor": null
}
```

### list_pending_time_off_requests

Time off requests waiting for approval in your BambooHR inbox, or in the company inbox for admins. Access: read. REST: `GET /api/v1/bamboohr/pending-time-off-requests`. MCP: `bamboohr_read → list_pending_time_off_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `scope` | string | no | 'assigned_to_me' or 'assigned_to_company'. Default: assigned_to_me. |

Returns the time off requests in the Time Off Requests section of the inbox that wait for a decision. Scope assigned_to_me lists requests where you are the next approver; assigned_to_company lists every pending request, which only works with admin access. Each request shows the employee, type, dates and the approval step it is on.

Example response:

```json
{
  "requests": [
    {
      "request_id": "to_5521",
      "employee_id": "431",
      "employee": "Lena Ortiz",
      "type": "Vacation",
      "start": "2026-11-02",
      "end": "2026-11-03",
      "days": 2,
      "step": "Level 1 of 2"
    },
    {
      "request_id": "to_5524",
      "employee_id": "418",
      "employee": "Tom Becker",
      "type": "Sick",
      "start": "2026-10-19",
      "end": "2026-10-21",
      "days": 3,
      "step": "Level 1 of 1"
    }
  ]
}
```

### add_task_lists

Import onboarding or offboarding task lists to an employee, as Add Task List(s) and Save Tasks do. Access: write, asks the user first. REST: `POST /api/v1/bamboohr/employees/{employee_id}/task-lists`. MCP: `bamboohr_write → add_task_lists`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee ID from find_employee. |
| `kind` | string | yes | Which checklist: 'onboarding' or 'offboarding'. |
| `list_ids` | string[] | yes | Task list IDs from list_task_lists. |
| `include_unmatched` | boolean | no | true also imports tasks whose filters do not include the employee. Default: false. |

Imports the chosen lists to the employee's Onboarding or Offboarding tab. By default only tasks whose filters include the employee are imported, the same as BambooHR's preselection, and the response says how many were filtered out. Assignees can be notified, on the timing set for each task. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "employee_id": "412",
  "kind": "onboarding",
  "lists_added": [
    {
      "list_id": "tl_it_setup",
      "name": "IT setup",
      "tasks_added": 4
    },
    {
      "list_id": "tl_manager",
      "name": "Manager tasks",
      "tasks_added": 3
    }
  ],
  "tasks_added_total": 7,
  "tasks_filtered_out": 0
}
```

### update_employee_task

Change who a task is assigned to or when it is due, on one employee's checklist. Access: write, asks the user first. REST: `PATCH /api/v1/bamboohr/tasks/{task_id}/employees/{employee_id}/task`. MCP: `bamboohr_write → update_employee_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee ID from find_employee. |
| `kind` | string | yes | Which checklist: 'onboarding' or 'offboarding'. |
| `task_id` | string | yes | Task ID from list_onboarding_tasks or list_offboarding_tasks. |
| `assignee_id` | string | no | Employee ID of the new assignee from find_employee. |
| `due_date` | string | no | New due date, YYYY-MM-DD. |

Changes the assignee, the due date or both on one task of an employee's Onboarding or Offboarding tab. Only the fields you pass change. The new assignee can be notified on the timing set for the task. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": "ot_9020",
  "task": "Schedule first-week 1:1",
  "assignee": "Sam Okafor",
  "due_date": "2026-10-19",
  "done": false
}
```

### complete_employee_task

Mark one onboarding or offboarding task done, or open it again. Access: write, asks the user first. REST: `POST /api/v1/bamboohr/tasks/{task_id}/employees/{employee_id}/task/complete`. MCP: `bamboohr_write → complete_employee_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee ID from find_employee. |
| `kind` | string | yes | Which checklist: 'onboarding' or 'offboarding'. |
| `task_id` | string | yes | Task ID from list_onboarding_tasks or list_offboarding_tasks. |
| `done` | boolean | no | false opens the task again. Default: true. |

Marks one task on an employee's Onboarding or Offboarding tab as done, or as open again when done is false. Use it for tasks finished outside BambooHR, such as a laptop shipped. People following the checklist see the new status. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": "ot_9012",
  "task": "Order laptop",
  "done": true
}
```

### request_signature

Send an e-signature template to one or more employees. Access: write, asks the user first. REST: `POST /api/v1/bamboohr/templates/{template_id}/signature/request`. MCP: `bamboohr_write → request_signature`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `template_id` | string | yes | Template ID from list_signature_templates. |
| `employee_ids` | string[] | yes | Employee IDs from find_employee. |

Requests a signature on the template from each employee in one call. Employees are notified and sign from their BambooHR inbox; the signed copy goes to the folder set in the template. An employee who already has a pending request for the same template is skipped and reported. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "template_id": "sg_handbook_2026",
  "requested": [
    {
      "request_id": "sr_7710",
      "employee_id": "412",
      "employee": "Ana Kowal"
    },
    {
      "request_id": "sr_7711",
      "employee_id": "418",
      "employee": "Tom Becker"
    },
    {
      "request_id": "sr_7712",
      "employee_id": "431",
      "employee": "Lena Ortiz"
    }
  ],
  "requested_total": 3,
  "skipped_pending": 0
}
```

### remind_signature_signers

Send a reminder for pending signature requests, as the Signed Documents report does. Access: write, asks the user first. REST: `POST /api/v1/bamboohr/signature-signers/remind`. MCP: `bamboohr_write → remind_signature_signers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_ids` | string[] | yes | Pending request IDs from list_signature_requests. |

Sends a reminder to the employee of each pending request you pass. Requests that were signed in the meantime are skipped and reported. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "reminded": [
    {
      "request_id": "sr_7701",
      "employee": "Ana Kowal"
    }
  ],
  "reminded_total": 1,
  "skipped_signed": 0
}
```

### decide_time_off_request

Approve or deny a time off request waiting for you. Access: write, asks the user first. REST: `POST /api/v1/bamboohr/requests/{request_id}/time-off-request/decide`. MCP: `bamboohr_write → decide_time_off_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request ID from list_pending_time_off_requests. |
| `decision` | string | yes | 'approve' or 'deny'. |
| `override` | boolean | no | true uses Approve Anyway as an admin when you are not the next approver. Default: false. |

Approves or denies one request from your inbox. In a multi-level approval workflow the request moves on to the next approver after your approval, and the employee is told only after the last one; a denial ends the process and the employee is told. As an admin who is not the next approver, set override to use Approve Anyway. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "to_5521",
  "employee": "Lena Ortiz",
  "decision": "approved",
  "next_step": "Level 2 of 2"
}
```

## How do I connect BambooHR to Claude Code, Codex or Cursor?

Connecting BambooHR takes three steps: sign up, sign in to BambooHR once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect BambooHR to your agent.

1. **Create an account** Sign up and add BambooHR in the console. Your API key is there too.

2. **Sign in to BambooHR in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to BambooHR there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the BambooHR tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Find employees in BambooHR who start in the next 7 days and have no onboarding tasks yet. Add the IT setup and Manager tasks lists, and tell me which tasks have no assignee.
```

### Call BambooHR from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/bamboohr with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/bamboohr/tasks/ot_9012/employees/412/task/complete \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"onboarding"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "task_id": "ot_9012",
  "task": "Order laptop",
  "done": true
}
```

## Why use Cotlet for BambooHR?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to BambooHR yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When BambooHR changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect BambooHR to Cotlet?

Yes. You sign in to BambooHR yourself, in your own Cloud Browser, and we never save your password. Your agents only get BambooHR once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official BambooHR integration?**

No, Cotlet is independent of BambooHR. BambooHR's own API is too limited for this work. Cotlet works through your own BambooHR account, the way you use BambooHR in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to BambooHR in your console: your agents lose access at once and you stay signed in. Signing out of BambooHR in the browser works too, and Reset browser deletes the whole profile.

## Is there a BambooHR MCP server on GitHub?

Yes. Community BambooHR MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it access to BambooHR and keep it running; when something changes, you or the maintainer fix it. A server built on the public API reaches only what the API exposes, which leaves out task lists and e-signatures. Cotlet hosts the server for you, works in your own signed-in session, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, give it access to BambooHR, add it to each MCP client | Sign up, sign in to BambooHR once, add one MCP server or API key |
| What it reaches | What the public API exposes: no task lists, no e-signature requests | What your account does in the BambooHR screens, including task lists and signatures |
| When BambooHR changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your BambooHR access | Stored on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you renew the key or sign in by hand | Your Cloud Browser keeps you signed in; if BambooHR logs you out, your agent gets a link to sign in again |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when BambooHR changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the BambooHR API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the BambooHR API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own BambooHR account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to BambooHR yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get BambooHR only after you enable it. When BambooHR signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to BambooHR, sign out of BambooHR in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **BambooHR's terms:** You use your own BambooHR account and stay responsible for following BambooHR's terms. Cotlet is independent and not affiliated with BambooHR. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open BambooHR in the console and press Request access. Then you create your API key and connect BambooHR there.

**Do I need to be technical?**

No. You sign in to BambooHR once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect BambooHR to Cotlet?**

Yes. You sign in to BambooHR yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get BambooHR once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My BambooHR sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your BambooHR cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through BambooHR's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. BambooHR sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no BambooHR login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

BambooHR offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**BambooHR has an MCP server. Do I still need Cotlet?**

For time off, employees and goals, the beta MCP is enough if your admin has turned on AI Connectors under Settings > Apps. It has no tools for onboarding and offboarding task lists or e-signature requests, and it lists files without their contents (checked 16 Oct 2026). Cotlet covers those jobs and works from your own signed-in session, so no admin switch is needed for it.

**Which BambooHR plan do I need?**

BambooHR's e-signature feature is included in the Core, Pro and Elite packages. BambooHR's API documentation does not say which plans include the API or the MCP server, and Cotlet needs only that your account can use the screens the tools act on.

**Can my agent post or send messages in BambooHR without asking me?**

No. Every call to add_task_lists, update_employee_task, complete_employee_task, request_signature, remind_signature_signers or decide_time_off_request waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the BambooHR API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/bamboohr from the HTTP Request node.

---

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.