fetch_employeesLABSCO SUMMARY
Payroll records become answerable questions.
It reads: employees, earnings, local taxes, pay statements and the code lists that decode them. Because the company IDs are fixed in configuration, the set of records an assistant can reach is decided before it starts rather than per call.
What it is
A read server over the Paylocity API. Six tools fetch employees, their details, earnings, local taxes and pay statements, plus the company code lists those records refer to. The same data is also addressable through a paylocity:// resource scheme.
What you get
- Every employee for a company
- Details for a specific employee
- Earnings data for an employee
- Local taxes for an employee
- Pay statement details for a given year and check date
- Company codes for a named code resource
- The same records reachable as paylocity:// resources
Requirements
Paylocity API credentials - a client ID and secret - plus the company IDs you want reachable and which API environment to use, production or testing. All are set as environment variables.
Setup effort
Follow the published steps
USE CASES
01
Answering a question about one person's pay
Pull their details, earnings and the pay statement for the date in question, instead of exporting a report to find one line.
02
Checking what happened on a specific pay date
Fetch the statement for that year and check date, with the employee list to identify who it belongs to.
03
Working out a local tax withholding
Read the local taxes on the employee record next to their details, so the jurisdiction and the amount arrive together.
04
Making sense of the codes on a record
Fetch the company code list for that resource and translate what the record refers to, rather than reading a raw identifier.
6 tools
Listed in project docs. Your client may show a different list.
fetch_employee_detailsfetch_employee_earningsfetch_company_codesfetch_employee_local_taxesfetch_employee_paystatement_detailsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation. Every tool is a fetch; nothing changes employee records or runs payroll. Six paylocity:// resources cover the same data.
Requires
- PAYLOCITY_CLIENT_ID in your environment
- PAYLOCITY_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Set PAYLOCITY_CLIENT_ID, PAYLOCITY_CLIENT_SECRET, PAYLOCITY_COMPANY_IDS and PAYLOCITY_ENVIRONMENT in a .env file in the project root directory
Add the mcpServers block to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%/Claude/claude_desktop_config.json)
MCP Clients
Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"mcpPaylocity": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_MCP_PAYLOCITY>",
"run",
"mcppaylocity"
]
}
}
}The configuration on this page does not set PAYLOCITY_CLIENT_ID and PAYLOCITY_CLIENT_SECRET; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
