Paychex MCP connector
The Paychex connector brings companies, workers, jobs, company checks and custom fields into Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients, so your team can look up and update Paychex records within each person's own access.
- App credentials
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which workers have custom fields missing for onboarding this week?
Working in Paychex with Elaichi
-
List all Paychex companies
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Paychex to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Paychex 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.
Paychex 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.
Paychex 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.
Paychex 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.
Paychex 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 Paychex 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 Paychex through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Paychex is logged.
-
HR
Pull up a worker before a conversation
Ask for a worker's Paychex record by their ID and get their details read back before a check-in or a difficult meeting, without clicking through the Paychex menus.
-
HR
Catch a worker record up after a change
When someone changes their name, address or other details, tell the agent and it updates the Paychex worker record while you move on to the next thing.
-
Payroll
Cut a company check when one is needed
Create a company check in Paychex for an off-cycle payment and review the list of existing checks before you do, all from the same chat.
-
Finance
Review calculation bases before a payroll run
List the calculation bases set up on a Paychex company and ask the agent to summarize them so the run is checked before money moves.
-
Operations
Add a new job to the company
When a new role is approved, create the job in Paychex and confirm the full list of jobs and employment types is up to date.
-
People Ops
Set up custom fields for tracking
Create custom fields and custom field categories in Paychex to track things like desk location or equipment, then tidy up old ones you no longer use.
Try asking
- “Which workers have custom fields missing for onboarding this week?”
- “Summarize company checks issued across all Paychex companies this month.”
- “List worker updates made in Paychex since Monday.”
What connecting Paychex gets you
6 screens from Elaichi, each doing one job for your Paychex account.
Ask Elaichi to work across your apps.
Which workers have custom fields missing for onboarding this week?
Summarize company checks issued across all Paychex companies this month.
List worker updates made in Paychex since Monday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask payroll questions, get worker answers instantly.
Type a question in plain language and pull answers straight from live Paychex records.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One Paychex endpoint, every client connects.
Claude, ChatGPT, Cursor and Microsoft Copilot all reach Paychex through one governed org endpoint, no shared keys.
ElaichiToolsTool catalog
112 Paychex tools, zero custom code.
Every Paychex tool, resource and method cataloged and ready to use without writing custom code.
ElaichiToolboxesToolboxes
Every team gets its own Paychex toolbox.
HR, payroll and finance each work from a toolbox scoped to their own Paychex needs.
ElaichiConnectionsShared connections
Delegated Paychex access, no shared passwords.
See who connected each Paychex account and how many teams and members share it.
ElaichiAudit logAudit log
Every Paychex change, logged and answerable.
See who did what in Paychex, when it happened, and which resource it 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. Automations, collections and live dashboards come with the Black plan.
Paychex digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch workers
Paychex
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
Paychex
Queued
Automations
A schedule triggers, Paychex work gets done.
Records are fetched, grouped, drafted into a digest, approved by a person, then posted back to Paychex.
Paychex health
Refreshed 4 minutes ago · every 15 minutes · from the workers collection
Workers
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Workers created
Last 14 days
By team
Share of activity
Corporate HR 34%
West Region 27%
East Region 21%
Contractors 18%
Collections and dashboards
Paychex health, refreshed on a schedule.
Four metrics and a 14 day chart of records created, broken down by team, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Paychex
All three can connect Paychex 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 Paychex tools | Allow or restrict single Paychex 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 Paychex 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.
Paychex tools for your AI agents
112 tools are ready to call through Elaichi's MCP endpoint the moment you connect Paychex, 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 Paychex to Claude?
First, connect Paychex in Elaichi: choose it from the catalog and enter the app credentials from your Paychex account, then Elaichi signs you in with them. There is no OAuth application to register and no client ID or secret to generate. Second, open Claude, go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Paychex is ready to use.
Does Paychex work with ChatGPT and Cursor as well as Claude?
Yes. Once Paychex is connected in Elaichi, 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 Paychex once and every client you use picks it up.
What can an AI agent actually do with my Paychex data?
With Paychex connected, an agent can list your companies, look up a worker's record, update that worker's details, create and review company checks, and add or look up jobs. It can also list calculation bases, contact types, employment types and document categories, and create, update or remove custom fields and their categories. Because Paychex offers so many actions, short concrete asks such as "update worker 4821's address" work better than long paragraphs.
Does connecting Paychex give the AI everything in my Paychex account?
No. Every request to Paychex runs as the person who signed in, so the agent sees only the companies and workers that person can already see in Paychex. Elaichi can narrow that further, for example by restricting updates or deletions for a role, but it can never widen access beyond what Paychex already allows that person.
Can I stop an agent from deleting or changing things in Paychex?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Paychex workers and jobs while restricting updates, deletions or creating company checks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Paychex connection when someone leaves?
When you offboard someone in Elaichi, their access to Paychex through every client ends at once. A shared Paychex connection keeps working for everyone else on the team. If you want to remove Paychex entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Paychex MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Paychex 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 Paychex?
Yes. Both let Claude, ChatGPT or Cursor use Paychex. 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 Paychex call.
How is Elaichi different from Composio for Paychex?
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 Paychex: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Paychex 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