Paylocity MCP connector
The Paylocity connector brings employees, jobs, earnings, deductions, cost centers and documents into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update payroll and HR records within their own Paylocity access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Paylocity to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Paylocity once
-
Open Connections, choose Add connection, and pick Paylocity.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Paylocity API key. One person generates a token in Paylocity and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Paylocity MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Paylocity MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Paylocity MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Paylocity to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Paylocity through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
HR
Brief yourself on an employee before a meeting
Ask for an employee's position, work location, cost center and pay frequency in Paylocity and have it in front of you before the conversation starts.
-
Payroll
Add a bonus to an employee's earnings
Create or update an employee earning in Paylocity from a plain request, then read it back to confirm it before the pay run closes.
-
Finance
Reconcile headcount by cost center
List employees, cost centers and positions in Paylocity and get a headcount breakdown ready for the monthly close, without exporting a spreadsheet.
-
Recruiting
Open the job as soon as it's approved
Create the job in Paylocity, update its details as the role changes, and remove it once the hire is made.
-
Operations
Check work locations and positions across sites
See every Paylocity work location and the positions tied to each, so office moves and reorganizations start from current records.
-
Leadership
Answer a compensation question without a spreadsheet
Ask which earnings, deductions and taxes are configured in Paylocity and get a plain answer instead of waiting on an export.
Try asking
- “List everyone in the Chicago work location with their positions”
- “Add a $500 bonus earning for Maria Chen this pay period”
- “Which jobs are still open in the Engineering cost center?”
AI tools
Paylocity tools for your AI agents
51 tools are ready to call through Elaichi's MCP endpoint the moment you connect Paylocity, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Paylocity gets you
6 screens from the product, each doing one job for your Paylocity account.
The agent
Ask about employees and earnings in plain language.
Answers come from live Paylocity employee, job and cost center records, not a stale export.
- employees
- jobs
- earnings
- deductions
Ask Elaichi to work across your apps.
List everyone in the Chicago work location with their positions
Add a $500 bonus earning for Maria Chen this pay period
Which jobs are still open in the Engineering cost center?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Paylocity in every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
51 Paylocity tools, no code to write.
Employees, jobs, earnings, deductions, taxes, cost centers and documents, listed with every method.
- List all Paylocity company info
- Get single Paylocity company info by ID
- List all Paylocity employees
- Get single Paylocity employee by ID
Toolboxes
Every team gets its own Paylocity toolbox.
Payroll sees earnings and deductions, Recruiting sees jobs, each scoped to what they need.
- HR
- Payroll
- Finance
- Recruiting
Shared connections
Share a Paylocity connection, never the key.
One person connects, teammates work through it, and nobody else ever sees a credential.
- HR
- Payroll
- Finance
- Recruiting
Audit log
Every Paylocity call is on the record.
When, who, what happened, type and resource, appended for every employee and earning touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the payroll digest itself.
New Paylocity earnings are fetched, grouped, drafted into a digest, approved, then posted back.
Paylocity digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch employees
Paylocity
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Paylocity
Queued
Collections and dashboards
Paylocity health, counted with no model involved.
Four metrics, 14 days of records created and a team breakdown, refreshed on a schedule.
Paylocity health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
HR 34%
Payroll 27%
Finance 21%
Recruiting 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Paylocity to Claude?
Connect Paylocity in Elaichi first: you paste in your Paylocity API key and the connection is ready, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Paylocity employees, jobs and earnings are available in the conversation.
Does Paylocity work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Paylocity once in Elaichi and every client picks it up.
What can an AI agent actually do with my Paylocity data?
It can look up employees, positions, work locations, cost centers, pay frequencies, deductions, taxes and company or employee documents in Paylocity, and answer questions about them in plain language. It can also create, update and delete jobs and employee earnings, such as adding a bonus or opening a new role. Short, concrete asks like "list employees in the Denver location" work better than long paragraphs.
Does connecting Paylocity give the AI access to every employee record?
No. Every call runs as the person who signed in, so the AI only sees the Paylocity employees, earnings and documents that person can already reach. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Paylocity itself allows.
Can I stop an agent from deleting or changing things in Paylocity?
Yes. Restrictions in Elaichi work per action, so you can allow reading Paylocity employees and earnings while blocking creating, updating or deleting jobs and earnings. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Paylocity connection when someone leaves?
Offboarding a person in Elaichi ends their access to Paylocity through every client at once. A shared Paylocity connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Paylocity once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the Paylocity MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Paylocity is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Paylocity in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.