[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) # PeopleHR API and MCP server > PeopleHR has a REST API, the Access PeopleHR Integration API v4.0, but no official MCP server (checked 22 Oct 2026). The API covers 31 resources and 150 actions, mostly employee records, holiday and absence data, and every call needs an API key that an HR admin creates in Settings. It has no action to approve or decline a holiday request and no resource for tasks. HR system from Access Group for UK and Irish companies: employee records, holiday and absence with approvals, tasks, saved queries and an employee portal. ## What is the PeopleHR API? Cotlet's PeopleHR API exposes 10 endpoints for your own PeopleHR account: list holiday requests, list employees, get employee, get employee planner, list tasks, list saved queries, run saved query, approve holiday request, decline holiday request and create task. The list_holiday_requests endpoint returns holiday requests as the Holiday tab of Authorisations shows them. Each endpoint takes simple JSON inputs like cursor, employee_id or request_id and works both as an operation of the peoplehr_read or peoplehr_write MCP tool for agents and as a REST call for scripts. - **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md) - **Endpoints:** 10 (7 read, 3 write) - **Updated:** 2026-10-20 PeopleHR has a REST API, the Access PeopleHR Integration API v4.0, but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for PeopleHR with 10 endpoints (7 read, 3 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does PeopleHR have an official API? PeopleHR has a REST API, the Access PeopleHR Integration API v4.0, but no official MCP server (checked 22 Oct 2026). The API covers 31 resources and 150 actions, mostly employee records, holiday and absence data, and every call needs an API key that an HR admin creates in Settings. It has no action to approve or decline a holiday request and no resource for tasks. | Task | PeopleHR official | Cotlet | |---|---|---| | List employees and read a profile | Yes: Employee API | Yes | | Read an employee's holidays and absences | Yes: Holiday and Absence APIs | Yes | | List holiday requests waiting for you | Partly: Holiday records carry a Status, but no action lists an approver's queue | Yes | | Approve or decline a holiday request | No | Yes | | Create a task for a colleague | No | Yes | | List tasks by status | No | Yes | | Run a saved query | Partly: Query API runs queries that already exist in your company; the Excel Hotsheets feature needs the API licence | Yes | Sources: [Access PeopleHR Integration API v4.0: Introduction](https://apidocs.peoplehr.com/), [Access PeopleHR Integration API v4.0: Overview](https://apidocs.peoplehr.com/overview.html), [Access PeopleHR Integration API v4.0: Employee Holiday](https://apidocs.peoplehr.com/holiday.html), [Zapier: People HR integrations](https://zapier.com/apps/people-hr/integrations) ## For AI agents ```text PeopleHR has a REST API, the Access PeopleHR Integration API v4.0, but no official MCP server (checked 22 Oct 2026). The API covers 31 resources and 150 actions, mostly employee records, holiday and absence data, and every call needs an API key that an HR admin creates in Settings. It has no action to approve or decline a holiday request and no resource for tasks. Cotlet provides a hosted MCP server and REST API for PeopleHR: 10 tools (7 read, 3 write). Access Sign up at https://cotlet.dev/app/signup?app=peoplehr, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools peoplehr_read, peoplehr_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/peoplehr, each operation at its own route, e.g. POST /api/v1/peoplehr/requests/{request_id}/holiday-request/approve Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_holiday_requests, list_employees, get_employee, get_employee_planner, list_tasks, list_queries, run_query, approve_holiday_request, decline_holiday_request, create_task Confirm approve_holiday_request, decline_holiday_request, create_task (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/peoplehr-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=peoplehr, requests PeopleHR in the Cotlet console and creates an API key there. 2. The user signs in to PeopleHR once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables PeopleHR 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 PeopleHR server that someone else maintains, including non-developers. 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 PeopleHR 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 PeopleHR 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 PeopleHR 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 PeopleHR's terms; Cotlet is not affiliated with PeopleHR. ``` ## What can an AI agent do in PeopleHR? Cotlet is best for HR admins and managers who use PeopleHR and want their AI agent to handle holiday approvals, onboarding tasks and saved-query reports without running or fixing a server. - **[Auto-approve holiday requests](https://cotlet.dev/integrations/peoplehr-api-mcp-server/approve-holiday-requests.md)** (runs: daily): "Go through my pending PeopleHR holiday requests. Approve requests of up to 3 days that start at least 14 days from now and leave nothing else for the person to cover. Decline requests that overlap our freeze week with a comment. List everything else for me." → `list_holiday_requests`, `get_employee_planner`, `approve_holiday_request`, `decline_holiday_request` - **[Assign onboarding tasks to new starters](https://cotlet.dev/integrations/peoplehr-api-mcp-server/assign-onboarding-tasks.md)** (runs: weekly): "For everyone who started in PeopleHR this week, create the onboarding tasks for their manager: book a 1:1, share the team handbook and confirm their equipment. Set the completion date to 7 days after their start. Skip tasks that already exist." → `list_employees`, `get_employee`, `list_tasks`, `create_task` - **Chase overdue tasks** (runs: daily): "List all overdue tasks in PeopleHR grouped by assignee, and create a reminder task for anyone with more than 3 overdue." → `list_tasks`, `create_task` - **Weekly team absence digest** (runs: weekly): "Every Monday, tell me who in my team is on holiday or absent this week, from the planner of each person." → `list_employees`, `get_employee_planner` - **Report probation endings from a saved query** (runs: weekly): "Run my saved query "Probation ending soon" and tell me who is on the list and when each probation ends." → `list_queries`, `run_query` ## Can PeopleHR automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a PeopleHR 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 auto-approve holiday requests, 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/peoplehr/holiday-requests. | 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/peoplehr/holiday-requests with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 10 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 PeopleHR. ### list_holiday_requests Holiday requests as the Holiday tab of Authorisations shows them. Access: read. REST: `GET /api/v1/peoplehr/holiday-requests`. MCP: `peoplehr_read → list_holiday_requests`. | Parameter | Type | Required | Description | |---|---|---|---| | `filter` | string | no | One of pending, all, decided, my_requests. Default pending. | | `cursor` | string | no | Next page cursor from the previous call. | Returns what the quick filters in Authorisations show: pending is the requests assigned to you as approver, all is every pending request in the company, decided is every decided request, my_requests is the ones set for you or already decided by you. Each request has the employee, dates, duration in days, the requester comment and the status. all and decided need an admin account. Example response: ```json { "requests": [ { "request_id": "hol-48210", "employee_id": "PW15", "employee": "Priya Nair", "start_date": "2026-11-16", "end_date": "2026-11-18", "duration_days": 3, "requester_comment": "Long weekend with family", "status": "Pending" }, { "request_id": "hol-48233", "employee_id": "PW22", "employee": "Lena Ortiz", "start_date": "2026-12-01", "end_date": "2026-12-10", "duration_days": 8, "requester_comment": "Family event", "status": "Pending" } ], "next_cursor": null } ``` ### list_employees Lists employees from the employee list. Access: read. REST: `GET /api/v1/peoplehr/employees`. MCP: `peoplehr_read → list_employees`. | Parameter | Type | Required | Description | |---|---|---|---| | `search` | string | no | Part of a name. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the employee ID, name, job title, department and start date of each person in the list your role can see. Leavers are not included. Use the employee ID in get_employee and get_employee_planner. Example response: ```json { "employees": [ { "employee_id": "PW41", "name": "Ana Lopez", "job_title": "Account Executive", "department": "Sales", "start_date": "2026-11-16" }, { "employee_id": "PW15", "name": "Priya Nair", "job_title": "Software Engineer", "department": "Engineering", "start_date": "2024-03-04" } ], "next_cursor": null } ``` ### get_employee Reads one employee's profile. Access: read. REST: `GET /api/v1/peoplehr/employees/{employee_id}`. MCP: `peoplehr_read → get_employee`. | Parameter | Type | Required | Description | |---|---|---|---| | `employee_id` | string | yes | Employee ID from list_employees, for example PW15. | Returns job title, department, line manager, start date and work email as the profile shows them to your role. Fields your role cannot open, such as salary, are left out. It reads only and changes nothing. Example response: ```json { "employee_id": "PW41", "name": "Ana Lopez", "job_title": "Account Executive", "department": "Sales", "line_manager": { "employee_id": "PW8", "name": "Dana Reyes" }, "start_date": "2026-11-16", "work_email": "ana.lopez@example.com" } ``` ### get_employee_planner Reads one employee's holidays or absences for a date range from their Planner tab. Access: read. REST: `GET /api/v1/peoplehr/employees/{employee_id}/planner`. MCP: `peoplehr_read → get_employee_planner`. | Parameter | Type | Required | Description | |---|---|---|---| | `employee_id` | string | yes | Employee ID from list_employees, for example PW15. | | `type` | string | yes | holidays or absences. | | `start_date` | string | yes | First day, YYYY-MM-DD. | | `end_date` | string | yes | Last day, YYYY-MM-DD. | Returns each entry in the range with its dates and duration in days, in date order. Holidays include the status of the request. Anything that deducts days from the entitlement, emergency leave included, shows up under holidays. Example response: ```json { "employee_id": "PW15", "type": "holidays", "entries": [ { "start_date": "2026-11-16", "end_date": "2026-11-18", "duration_days": 3, "status": "Pending" }, { "start_date": "2026-11-26", "end_date": "2026-11-27", "duration_days": 2, "status": "Approved" } ] } ``` ### list_tasks Lists tasks from the Tasks area. Access: read. REST: `GET /api/v1/peoplehr/tasks`. MCP: `peoplehr_read → list_tasks`. | Parameter | Type | Required | Description | |---|---|---|---| | `view` | string | no | mine or all. Default mine. all shows every task in the company to an admin, and the tasks you assigned to your team to a manager. | | `status` | string | no | One of overdue, new, due_today, upcoming, completed. Default all of them. | | `cursor` | string | no | Next page cursor from the previous call. | Returns title, assignee, the employee the task is about, completion date and status of each task, grouped like the Tasks area: overdue, new, due today, upcoming, completed. Tasks without a completion date are never overdue. Example response: ```json { "tasks": [ { "task_id": "tsk-3301", "title": "Confirm equipment", "assignee": "Dana Reyes", "about": "Ana Lopez", "completion_date": "2026-11-23", "status": "New" }, { "task_id": "tsk-3188", "title": "Collect signed contract", "assignee": "Sam Okafor", "about": "Jake Ortiz", "completion_date": "2026-11-10", "status": "Overdue" } ], "next_cursor": null } ``` ### list_queries Lists the saved queries in HR Admin > Queries. Access: read. REST: `GET /api/v1/peoplehr/queries`. MCP: `peoplehr_read → list_queries`. No parameters. Returns the name, category and description of each saved query you can open. It needs an HR Admin account. Queries are built in PeopleHR; this tool does not create or edit them. Example response: ```json { "queries": [ { "name": "Probation ending soon", "category": "Employment", "description": "Probation end date in the next 28 days" }, { "name": "Sickness this quarter", "category": "Absence", "description": "Sick days by employee" } ] } ``` ### run_query Runs a saved query and returns its rows. Access: read. REST: `GET /api/v1/peoplehr/queries/run`. MCP: `peoplehr_read → run_query`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | Exact name from list_queries. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the columns of the query and its rows as PeopleHR shows them, the same data the Export to CSV button gives. Dates keep the format PeopleHR uses in the result. It reads only and changes nothing. Example response: ```json { "name": "Probation ending soon", "columns": [ "Employee", "Probation End Date", "Probation Status" ], "rows": [ [ "Ana Lopez", "2027-02-16", "In probation" ], [ "Jake Ortiz", "2026-12-04", "In probation" ] ], "next_cursor": null } ``` ### approve_holiday_request Approves a holiday request that is assigned to you. Access: write, asks the user first. REST: `POST /api/v1/peoplehr/requests/{request_id}/holiday-request/approve`. MCP: `peoplehr_write → approve_holiday_request`. | Parameter | Type | Required | Description | |---|---|---|---| | `request_id` | string | yes | Request ID from list_holiday_requests. | | `comment` | string | no | Comment the employee sees with the decision. | Approves the request as the account that is signed in, which must be its approver. PeopleHR then tells the employee in Feed. A decided request cannot be changed: it has to be deleted and submitted again. A request that is already decided fails with an error. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "request_id": "hol-48210", "employee": "Priya Nair", "start_date": "2026-11-16", "end_date": "2026-11-18", "status": "Approved", "decided_by": "Dana Reyes", "comment": "Approved, enjoy the break." } ``` ### decline_holiday_request Declines a holiday request that is assigned to you. Access: write, asks the user first. REST: `POST /api/v1/peoplehr/requests/{request_id}/holiday-request/decline`. MCP: `peoplehr_write → decline_holiday_request`. | Parameter | Type | Required | Description | |---|---|---|---| | `request_id` | string | yes | Request ID from list_holiday_requests. | | `comment` | string | no | Reason the employee sees with the decision. | Declines the request as the account that is signed in, which must be its approver. PeopleHR then tells the employee in Feed, so give a reason in the comment. A decided request cannot be changed: it has to be deleted and submitted again. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "request_id": "hol-48233", "employee": "Lena Ortiz", "start_date": "2026-12-01", "end_date": "2026-12-10", "status": "Declined", "decided_by": "Dana Reyes", "comment": "Freeze week, please pick other dates." } ``` ### create_task Creates a task and assigns it to an employee. Access: write, asks the user first. REST: `POST /api/v1/peoplehr/assignees/{assignee_id}/tasks`. MCP: `peoplehr_write → create_task`. | Parameter | Type | Required | Description | |---|---|---|---| | `title` | string | yes | Task title. | | `assignee_id` | string | yes | Employee ID of the person who does the task. | | `about_employee_id` | string | no | Employee ID the task is in relation to, for example a new starter. | | `completion_date` | string | no | Completion date, YYYY-MM-DD. Optional. | | `description` | string | no | What to do. | Creates the task from the plus icon in the Tasks area. An admin can assign it to anyone, a manager only to employees who report to them, and PeopleHR refuses someone who is leaving. Documents cannot be attached to a task. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "task_id": "tsk-3301", "title": "Book first 1:1", "assignee": "Dana Reyes", "about": "Ana Lopez", "completion_date": "2026-11-23", "status": "New" } ``` ## How do I connect PeopleHR to Claude Code, Codex or Cursor? Connecting PeopleHR takes three steps: sign up, sign in to PeopleHR 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 PeopleHR to your agent. 1. **Create an account** Sign up and add PeopleHR in the console. Your API key is there too. 2. **Sign in to PeopleHR in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to PeopleHR 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 PeopleHR 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. ``` Go through my pending PeopleHR holiday requests. Approve requests of up to 3 days that start at least 14 days from now and leave nothing else for the person to cover. Decline requests that overlap our freeze week with a comment. List everything else for me. ``` ### Call PeopleHR 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/peoplehr 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/peoplehr/requests/hol-48210/holiday-request/approve \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"comment":"Approved, enjoy the break."}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "request_id": "hol-48210", "employee": "Priya Nair", "start_date": "2026-11-16", "end_date": "2026-11-18", "status": "Approved", "decided_by": "Dana Reyes", "comment": "Approved, enjoy the break." } ``` ## Why use Cotlet for PeopleHR? **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 PeopleHR 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 PeopleHR changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect PeopleHR to Cotlet? Yes. You sign in to PeopleHR yourself, in your own Cloud Browser, and we never save your password. Your agents only get PeopleHR 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 PeopleHR integration?** No, Cotlet is independent of PeopleHR. PeopleHR's own API is too limited for this work. Cotlet works through your own PeopleHR account, the way you use PeopleHR 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 PeopleHR in your console: your agents lose access at once and you stay signed in. Signing out of PeopleHR in the browser works too, and Reset browser deletes the whole profile. ## Is there a PeopleHR MCP server on GitHub? The realistic option is the PeopleHR API itself. It is well documented and reads employees, holiday and absence data well. You still build the MCP layer around it, and it cannot approve a request or create a task. Zapier has two triggers, New Starter and New Leaver, and no actions. Cotlet works in the signed-in app, so it does what an HR admin or manager does in the screens, and our team keeps it working. | | PeopleHR API | Cotlet | |---|---|---| | Setup | An HR admin creates an API key in Settings and ticks the endpoints it may use, then you write the MCP server or script | Sign up, sign in to PeopleHR once, add one MCP server or API key | | When PeopleHR changes | You update your wrapper; the API docs say v4.0 changed no endpoint paths or field names | Our team tests it daily and fixes it for you; failed calls are free | | Your PeopleHR access | A key tied to your company, limited to the endpoints you ticked, optionally to listed IP addresses | Your own login in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When access ends | Calls fail until an admin issues a key again | Your Cloud Browser keeps you signed in; if PeopleHR logs you out, your agent gets a link to sign in again | | Approvals and tasks | Not in the API: no approve or decline action, no tasks resource | Approve or decline holiday requests and create tasks as you do in the app | | Rate limit | Set by Access per company, not per key; ask support for your number | One browser session, one action at a time | | Price | Check with Access whether your plan includes the API licence | 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 PeopleHR 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 PeopleHR API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the PeopleHR 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 PeopleHR 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 PeopleHR 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 PeopleHR only after you enable it. When PeopleHR 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 PeopleHR, sign out of PeopleHR 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. - **PeopleHR's terms:** You use your own PeopleHR account and stay responsible for following PeopleHR's terms. Cotlet is independent and not affiliated with PeopleHR. [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 PeopleHR in the console and press Request access. Then you create your API key and connect PeopleHR there. **Do I need to be technical?** No. You sign in to PeopleHR 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 PeopleHR to Cotlet?** Yes. You sign in to PeopleHR yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get PeopleHR 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 PeopleHR 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 PeopleHR 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 PeopleHR's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. PeopleHR 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 PeopleHR 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?** PeopleHR 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). **Do I need the PeopleHR API licence?** No. Cotlet works in your own PeopleHR login and does not use an API key. Your role still counts: approving needs you to be the approver of the request, and saved queries need HR Admin. PeopleHR's help center says its Excel Hotsheets need the API licence, and Access can tell you what your plan includes. **What is the rate limit of the PeopleHR API?** It is set by Access for each company, not per key, and some companies have none. The API docs (checked 22 Oct 2026) say there is no universal default. A throttled call answers HTTP 200 with Status 5, and you ask support for your number. Cotlet works in one browser session and does not use that limit. **Can my agent post or send messages in PeopleHR without asking me?** No. Every call to approve_holiday_request, decline_holiday_request or create_task 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 PeopleHR 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/peoplehr 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.