Access PeopleHR

Getting the API key: in PeopleHR open Settings > API and create a key (a GUID such as 1a2b3c4d-...). When you create it you choose which resources (schemas) and which actions it may call: tick at least Employee, Holiday, Absence, Holiday Entitlements, Salary, Query Builder, Appraisal, Training and ATS for the read tools here, and add the Add Holiday / Add Absence actions only if you want the write tools. Put the key in PEOPLEHR_API_KEY. If the key has an IP allow-list, calls from AnythingMCP are refused unless its address is on it.

How the API works: every call is a POST to https://api.peoplehr.net/<Resource> (/Employee, /Holiday, /Absence, /Salary, /Query ...) with a JSON body holding APIKey, Action and the action's fields. The tools fill in the key and the action for you, so every read tool is a POST that only reads.

Errors come back as HTTP 200 with a Status code in the body (0 success, 10 no records found, 5 validation error or Access Denied., 6 server error). The connector reads Status and reports every code other than 0 and 10 as a failed call with PeopleHR's Message, so a wrong key or a missing grant shows up as an error rather than as data. Status 10 stays a normal answer: nothing matched. Access Denied. means the key is not granted that action or schema (an unknown action name gives the same answer); ask the PeopleHR admin to add the grant.

Ids: employees are addressed by their PeopleHR EmployeeId (e.g. PW15, max 15 characters). Start with peoplehr_get_employee_directory to find someone by name, then call the per-employee tools. Vacancies use their Reference (from peoplehr_list_vacancies), appraisals their AppraisalId.

Dates are yyyy-MM-dd. Other formats are either rejected or read day-first, so never send MM/dd/yyyy or an ISO date-time.

Volumes and paging: only peoplehr_list_employees pages (limit up to 500, offset in rows, Result.Pagination.TotalRows). The peoplehr_list_* tools for absences, holidays and salaries return the whole company in one answer, keyed by EmployeeId; narrow them with a date window.

Employee fields are wrapped: "FirstName": {"DisplayValue": "Jane", "FieldHistory": []}. EmployeeStatus is "1" for current staff and "2" for leavers.

Tenant settings decide some answers: peoplehr_list_leavers needs a separate GetAllLeavers grant even on a key with every other Employee action, and the vacancy and applicant tools need the recruitment (ATS) module to be active; otherwise both answer Status 5.

Query Builder: peoplehr_run_query runs a saved query by its exact name; the API cannot list queries, so ask the user for the name as it appears under Reports > Query Builder.

Rate limit: set per company by Access, not per key. A throttled call is Status 5 with a message like "API calls will be limited to a N per minute"; wait a minute and retry.