PeopleHR MCP Server

Approve holiday requests, assign tasks and run saved queries in PeopleHR.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/peoplehr'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

PeopleHR API and MCP server: Let your AI agent work the PeopleHR authorisations.

Access Group publishes no PeopleHR MCP server (checked 27 Oct 2026). The Integration API v4.0 documents 150 actions across 31 resources, read and write, on an API key an HR admin creates. It covers 4 of our 10 tools in full and 1 in part. Cotlet runs all 10 hosted, over MCP for agents and REST for scripts.

Approve holiday requests, assign tasks and run saved queries in PeopleHR. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by PeopleHR. PeopleHR is a trademark of its owner. If PeopleHR's own integrations cover what you need, use them first.

What can you automate in PeopleHR?

  • Approve holiday that fits your rule
  • Decline requests in a freeze week
  • Give new starters their onboarding tasks
  • Chase overdue tasks by assignee
  • Say who is off this week
  • Run a saved query and read the rows

Does PeopleHR have an MCP server or an API?

  • The Holiday resource adds, moves and deletes bookings; the status, approver and approver comments come back read only. No action approves or declines, and none lists the queue waiting on one approver.
  • There is no tasks resource. Query Builder runs a saved query by its exact, case-sensitive name, and the docs say no action lists those names.
  • Zapier has 2 triggers (New Starter, New Leaver) and no actions; Make has one module that watches events. Make says the API needs the API licence switched on for your account.
What you needPeopleHR APIAnythingMCP connectorCotlet
Read employees, holiday, saved queriesYesYes, 24 readsYes
List the requests waiting on youStatus per recordStatus per recordYes, Pending filter
Approve or decline holidayNoNoYes, after your OK
Create and list tasksNoNoYes
Works without an API keyHR admin keyHR admin keyYour own login

Checked 27 Oct 2026. Sources: Access PeopleHR Integration API v4.0: Introduction, Access PeopleHR Integration API v4.0: Overview, Access PeopleHR Integration API v4.0: Employee Holiday, Zapier: People HR integrations, Access PeopleHR Integration API v4.0: Query Builder, Make: People HR, AnythingMCP: Access PeopleHR to MCP, PeopleHR pricing

How does Cotlet connect to PeopleHR?

  1. Sign in to PeopleHR. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your PeopleHR password, and no decision or task reaches a colleague until you approve it.

Connect PeopleHR to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Sign in to PeopleHR in a Cloud Browser. Create a Cotlet account, open PeopleHR in its Cloud Browser, sign in on your company address as the approver or HR Admin, and press Enable for agents.
  2. Add the Cotlet address. Give your agent https://cotlet.dev/mcp/v1 as a remote MCP server or custom connector.
  3. Approve the connection. Chat apps show a Cotlet sign-in once. Code editors, n8n and scripts send an API key from the console.

https://cotlet.dev/mcp/v1 carries PeopleHR next to your other apps. Sign in as the person PeopleHR routes requests to: by default an approver sees direct reports only, and saved queries and company-wide tasks need HR Admin. No API key or API licence is involved. After you enable PeopleHR, refresh the connector so its tools load.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

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

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

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

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: peoplehr_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: peoplehr_write

How to use the PeopleHR REST API

Create your Cotlet API key

Create a Cotlet API key with access to PeopleHR and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect PeopleHR in Cotlet and enable it for agents. Account access: Your own PeopleHR login on your company address (HR Admin for queries and company-wide tasks, a manager for approvals and tasks for your team). What your agent can do follows your role. You sign in in your own browser and keep your SSO or 2-step verification.

Make your first PeopleHR API request

REST:

curl https://cotlet.dev/api/v1/peoplehr/holiday-requests \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read holiday requests and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "peoplehr",
  "tool": "list_holiday_requests",
  "result": {
    "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
  }
}

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.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

PeopleHR workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestReads one employee's holidays or absences for a date range from their Planner tab. Use get_employee_planner in your configured team report.
MakeHTTP > Make a requestLists employees from the employee list. Use list_employees in your configured team report.
Python or Node.jsREST APILists tasks from the Tasks area. Use list_tasks in your configured team report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads PeopleHR; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

PeopleHR API endpoints and MCP tools

Holiday requests

The four quick filters of Authorisations. A decision works only for the request's approver, and PeopleHR will not change a decided request.

  • List holiday requests (list_holiday_requests, read): Holiday requests as the Holiday tab of Authorisations shows them.
  • Approve holiday request (approve_holiday_request, write, asks first): Approves a holiday request that is assigned to you.
  • Decline holiday request (decline_holiday_request, write, asks first): Declines a holiday request that is assigned to you.

Employees and planner

Leavers are left out. Fields your role cannot open, salary for example, are not returned.

  • List employees (list_employees, read): Lists employees from the employee list.
  • Get employee (get_employee, read): Reads one employee's profile.
  • Get employee planner (get_employee_planner, read): Reads one employee's holidays or absences for a date range from their Planner tab.

Tasks

A manager assigns only to direct reports, an admin to anyone. PeopleHR refuses a task for someone who is leaving, and tasks take no attachments.

  • List tasks (list_tasks, read): Lists tasks from the Tasks area.
  • Create task (create_task, write, asks first): Creates a task and assigns it to an employee.

Saved queries

Runs queries already built in HR Admin > Queries; nothing is created or edited. HR Admin only.

  • List saved queries (list_queries, read): Lists the saved queries in HR Admin > Queries.
  • Run saved query (run_query, read): Runs a saved query and returns its rows.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/peoplehr-api-mcp-server#tools

Who can see my PeopleHR session, and how do I revoke it?

  • What we store. The signed-in PeopleHR browser profile, AES-256-GCM encrypted, in Finland. No password.
  • What your agent gets. The 10 PeopleHR tools. Never the session cookie.
  • What the session sees. What your PeopleHR role sees. For an HR Admin that is the whole company.
  • What no tool touches. Salaries, payroll, documents, appraisals and right to work checks.
  • Two-step sign-in and SSO. You pass them yourself in the Cloud Browser. We never do it for you.
  • How to cut access. Disable for agents, reset the browser, or change your PeopleHR password.

PeopleHR holds employee personal data, so check that your privacy notice covers a processor working in the HR account. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Reads the queue. list_holiday_requests with the Pending filter: requests routed to you.
  2. Checks the planner. get_employee_planner for the month around the dates.
  3. Waits for your OK. Each approve or decline shows up in your Cotlet console first.
  4. Reports back. Approved, declined with the comment, and the ones left for you.
ActionUndo
Approve holidayNo; delete the booking and resubmit
Decline holidayNo; the employee requests again
Create a taskMark it completed in Tasks
Run a saved queryNothing to undo, read only

3 of 10 tools ask first: the two decisions and every new task, because a colleague sees each one in Feed. Reads run at once. Switch the wait off per tool once a rule has proved itself, for example one-day requests with a month of notice.

PeopleHR does not let anyone change a decided authorisation, so an unclear request stays with you.

MCP call:

{
  "name": "approve_holiday_request",
  "arguments": {
    "request_id": "hol-48210",
    "comment": "Approved, enjoy the break."
  }
}

REST:

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."}'

Response:

{
  "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."
}

A cron job or an HTTP step calls the same tools over REST at /api/v1/peoplehr, one key, one price. A decision on a request routed to someone else fails with APP_PERMISSION_DENIED and costs nothing. The tools table gives the REST path of each tool.

How much does the PeopleHR MCP server cost?

About $18 a month for an 80-person company, 3,040 credits. Your PeopleHR plan is billed as before.

JobCallsCredits
Read the pending holiday queue, daily1 × 30300
Check the planner, then decide2 × 47940
"Off this week" saved query, Mondays1 × 440
Onboarding tasks per new starter5 × 2100
Chase overdue tasks, weekly3 × 4120
Probation report from a saved query1 × 440
Cloud Browser, 30 days1,500
Total3,040
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • One-time packs, valid 12 months, no subscription

Most PeopleHR reviewers on Software Advice UK work at companies of 51 to 200 people. With 5.6 weeks of UK leave, about 7 requests per person a year makes the 47 a month in the table. For scale, PeopleHR Starter for 80 people is £320 a month (£4 per employee, 27 Oct 2026). Dollars at the $29 pack rate.

PeopleHR MCP server: AnythingMCP, Apideck or hosted

OptionWhat it doesWhere it stops
AnythingMCP26 PeopleHR tools on one API key: 24 reads, including salaries and saved queries, plus booking holiday and absence. Open source (HelpCode-ai/anythingmcp, 752 stars, AGPL-3.0) or hosted.No approve, decline or tasks; needs the API licence and an HR admin key.
Apideck MCPUnified HRIS tools for employees and time off requests across many HR systems.Two resources, built for software vendors that connect many HR systems.
CyclrEmbedded integration connector on the same API key.For SaaS vendors; the same gaps as the API.
GitHubNo PeopleHR MCP server found. Clients only, such as ballerina-platform/module-ballerinax-peoplehr (102 stars) and the vendor's PeopleHR/PeopleHRExport.Code you host and wrap yourself.

For a nightly sync of employees or a holiday report into a spreadsheet, the official API or AnythingMCP does it on a key and costs you no browser. When the agent should clear the Authorisations queue, set tasks for new starters, or work for a manager who has no API key, Cotlet covers that part.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the PeopleHR tools.

PeopleHR API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open PeopleHR under Integrations in the console and sign in to PeopleHR in its Cloud Browser. The trial starts when you sign up, and no card is asked.

How do I connect PeopleHR to ChatGPT or Claude?

Sign up at cotlet.dev, log in to PeopleHR once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your PeopleHR account through Cotlet, in their phone apps too.

What can ChatGPT do in PeopleHR?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in PeopleHR: auto-approve holiday requests; assign onboarding tasks to new starters; chase overdue tasks. You ask in plain words, and anything that reaches other people waits for your OK first.

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.

Does PeopleHR have webhooks?

Yes, one URL per company under Settings > API, with events such as New Holiday Request and Holiday Approved (API docs, 27 Oct 2026). They only notify: delivery can take 10 minutes or more and a failed one gets a single attempt. An agent run on a schedule that reads the Pending queue does not depend on them.

Does it work with SSO or two-step verification?

Yes. You complete SSO or the code yourself when you sign in in the Cloud Browser, and the session stays signed in. If PeopleHR asks again, your agent gets a link and you sign in again.

Is the MCP server different from the REST API?

No, only the way in. Both carry the same 10 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with PeopleHR?

No. Cotlet is independent and not affiliated with The Access Group or Access PeopleHR.

Can I use the PeopleHR API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

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.