Paylocity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYLOCITY_ENV | Yes | The Paylocity environment (e.g., production). | |
| PAYLOCITY_CLIENT_ID | Yes | WebLink API Client ID used for employee details, pay statements, and write operations. | |
| PAYLOCITY_COMPANY_ID | Yes | The numeric ID Paylocity assigned to your company. | |
| PAYLOCITY_CLIENT_SECRET | Yes | WebLink API Client Secret. | |
| PAYLOCITY_NEXTGEN_CLIENT_ID | Yes | NextGen API Client ID used for the employee directory search. | |
| PAYLOCITY_NEXTGEN_CLIENT_SECRET | Yes | NextGen API Client Secret. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_employeesA | Search the employee directory by name, job title, email, or employee ID. Returns matching employees with basic info (name, title, department, status, supervisor). Use this first to find someone's employee ID, then use get_employee for full details. |
| get_employeeA | Get full details for an employee by ID. Returns everything: personal info, job/department, pay rate, tax setup, benefits, addresses, emergency contacts. SSN, FEIN, and bank info are redacted. |
| get_pay_statementsA | Get pay statement data for an employee by year. Returns both summary (gross pay, net pay, hours, direct deposit amounts) and line-item details (each tax, deduction, and earning). Optionally filter to a specific check date. |
| get_direct_depositA | Get direct deposit accounts for an employee. Account and routing numbers are redacted — shows account type, status, and name on account. |
| get_company_summaryA | Get a high-level workforce summary: total headcount, breakdown by status, department (with names), job title, and reporting relationships. |
| update_employeeA | Update an employee's information. Supports changing: personal info (name, address), job details (title, department, cost center, supervisor), compensation (pay rate, salary), employment status (active, terminated, leave), and benefit setup. All changes require an effective date where applicable. |
| add_earningsA | Add a one-time or recurring earning to an employee (bonus, commission, stipend, overtime, etc.). Use get_company_codes or check existing earnings for valid earning codes. |
| add_employeeA | Add a new employee to the system (onboarding). Creates the employee record with personal info, job details, and compensation. SSN is required by Paylocity but will not be stored in conversation — pass it directly and it will be sent encrypted. Returns the new employee ID. |
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 8 tools
Each tool targets a distinct domain concept with clear boundaries: employee CRUD (add/get/update/search), earnings management (add), payroll data (pay statements, direct deposit), and company insights. No overlapping functionality between tools like 'add_earnings' and 'update_employee'.
Strict adherence to verb_noun snake_case convention throughout (add_earnings, get_employee, search_employees, update_employee). Pluralization choices logically match the resource type (earnings, statements as collections; employee, deposit as singular records).
Eight tools provide a focused but sufficient surface for core HRIS operations without bloat. The scope covers employee lifecycle management, compensation adjustments, and payroll inquiry—appropriate for a Paylocity integration without attempting to wrap the entire API.
Solid CRUD coverage for employee records and read access to payroll data. Minor gaps exist: direct deposit can be viewed but not updated, and earnings can be added but not removed or modified. However, core 'find employee, view details, update info' workflows are fully supported.