peopleforce-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEOPLEFORCE_API_KEY | Yes | Your PeopleForce Company API key. | |
| PEOPLEFORCE_BASE_URL | No | Override if PeopleForce hosts you on a non-default endpoint. | https://app.peopleforce.io/api/public/v3 |
| PEOPLEFORCE_TIMEOUT_MS | No | Per-request timeout. | 15000 |
| PEOPLEFORCE_MAX_RETRIES | No | Max automatic retries for 429 / 5xx / network timeouts. | 3 |
| PEOPLEFORCE_RETRY_BASE_MS | No | Base for exponential backoff with full jitter. | 500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| peopleforce_list_employeesA | List employees with pagination. Only the |
| peopleforce_find_employee_by_emailA | Find a single employee by work or personal email. Paginates internally until a match is found. Returns the full employee object or null. |
| peopleforce_get_employeeA | Get a single employee by PeopleForce id. Returns full profile including position, department, manager, custom fields. |
| peopleforce_list_employee_positionsA | List position history for a specific employee (promotions, role changes, compensation). |
| peopleforce_list_leave_requestsA | List leave/time-off requests. Useful for 'who's on vacation', balance queries, approvals. Supports employee_id and state filters. |
| peopleforce_list_departmentsA | List all departments with manager and parent info. |
| peopleforce_list_positionsA | List all position titles used in the company. |
| peopleforce_list_locationsA | List office/remote locations. |
| peopleforce_list_divisionsB | List organizational divisions. |
| peopleforce_list_teamsB | List teams (cross-functional groupings). |
| peopleforce_list_holidaysB | List official company holidays. |
| peopleforce_list_job_levelsA | List job levels (Junior/Middle/Senior/etc). |
| peopleforce_list_job_profilesB | List job profiles (role descriptions). |
| peopleforce_list_legal_entitiesA | List legal entities employees are contracted under. |
| peopleforce_list_employment_typesA | List employment types (Full-time, Part-time, Contractor, etc). |
| peopleforce_list_gendersA | List gender reference values used in profiles. |
| peopleforce_list_skillsB | List skills tracked in the skills matrix. |
| peopleforce_list_competenciesA | List competencies used in performance reviews. |
| peopleforce_list_assetsB | List all assets/equipment in the company. |
| peopleforce_list_leave_typesA | List leave/time-off types (Vacation, Sick, Optional holiday, etc) with units and colors. |
| peopleforce_list_tasksA | List tasks assigned across the organization (onboarding, offboarding, HR actions). |
| peopleforce_list_recruitment_vacanciesA | List open and closed vacancies in the ATS. |
| peopleforce_list_recruitment_candidatesA | List candidates in the ATS pipeline. |
| peopleforce_list_recruitment_pipelinesA | List recruitment pipelines with their stages. |
| peopleforce_list_recruitment_sourcesA | List recruitment sources (where candidates came from). |
| peopleforce_list_employee_documentsB | List documents attached to a specific employee's profile. |
| peopleforce_list_employee_assetsA | List assets/equipment assigned to a specific employee. |
| peopleforce_api_requestA | Escape hatch: perform a raw GET against any PeopleForce v3 API path (relative to /api/public/v3). Use when no dedicated tool covers the endpoint. Example path: 'employees/12345' or 'leave_requests?state=approved'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Each tool targets a distinct entity or action. List tools all differ by the entity they list (e.g., assets, competencies, departments), and lookup tools (get, find) are clearly separated from lists. No overlap in purpose.
All tools follow a consistent pattern: 'peopleforce_' + verb (list, get, find) + '_' + entity. The verb clearly indicates the action, and all names use lowercase with underscores, ensuring predictability.
With 28 tools, the server exceeds the typical well-scoped range of 3-15 and falls into the 'too many' category (25+). While the HR domain has many entities, the sheer number of list tools feels excessive, especially since many are simple reference data lookups.
The tool set is heavily skewed towards read-only list operations. Missing dedicated create/update/delete tools for core entities like employees and leave requests, forcing agents to rely on the raw API escape hatch. This leaves significant gaps in typical HR workflows.