Paylocity MCP connector
The Paylocity connector brings employees, jobs, earnings, deductions, cost centers and documents into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and update payroll and HR records within their own Paylocity access.
- App credentials
- Free 14-day trial
- No credit card
List everyone in the Chicago work location with their positions
Working in Paylocity with Elaichi
-
List all Paylocity company info
-
Get single Paylocity company info by ID
-
List all Paylocity employees
How to connect Paylocity to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Paylocity MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Paylocity through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Paylocity is logged.
-
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?”
What connecting Paylocity gets you
6 screens from Elaichi, each doing one job for your Paylocity account.
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, Cursor or Microsoft Copilot
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.
Copy the endpoint
AI apps
One endpoint puts Paylocity in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
51 Paylocity tools, no code to write.
Employees, jobs, earnings, deductions, taxes, cost centers and documents, listed with every method.
Toolboxes
Every team gets its own Paylocity toolbox.
Payroll sees earnings and deductions, Recruiting sees jobs, each scoped to what they need.
Shared connections
Share a Paylocity connection, never the key.
One person connects, teammates work through it, and nobody else ever sees a credential.
Audit log
Every Paylocity call is on the record.
When, who, what happened, type and resource, appended for every employee and earning touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Paylocity digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Paylocity
Queued
Workflows
A schedule starts the payroll digest itself.
New Paylocity earnings are fetched, grouped, drafted into a digest, approved, then posted back.
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%
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.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Paylocity
All three can connect Paylocity to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Paylocity tools | Allow or restrict single Paylocity tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Paylocity call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting creating, updating or deleting jobs and earnings. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Paylocity?
Yes. Both let Claude, ChatGPT or Cursor use Paylocity. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Paylocity call.
How is Elaichi different from Composio for Paylocity?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Paylocity: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Paylocity in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot