Dayforce MCP connector
The Dayforce connector brings employee addresses, tax records, badges and availability into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update Dayforce records inside their own access, with every action logged.
-
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 Dayforce to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Dayforce once
-
Open Connections, choose Add connection, and pick Dayforce.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Dayforce API key. One person generates a token in Dayforce 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.
Dayforce 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.
Dayforce 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.
Dayforce 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 Dayforce 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 Dayforce through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
HR
Update an employee address after a move
When someone tells HR they have moved, the new address goes straight into their Dayforce record without opening a form. Ask for everyone whose address changed this month to check the mailing list.
-
Payroll
Set up tax details for new hires
Create federal and state tax records for a batch of new Canadian or Australian hires in one ask, then list what was created to confirm nothing was missed before the first pay run.
-
Payroll
Correct tax statuses across many employees
When a rule changes, update tax statuses for a whole group in Dayforce at once instead of one record at a time. Pull the list afterward to confirm every affected person was covered.
-
Operations
Check availability before building the schedule
Look up a person's availability in Dayforce while planning next week, so shifts land on days they can actually work. Managers get the answer in plain language without leaving their chat window.
-
Facilities
Issue and track building badges
Create a Dayforce badge for a new starter and list badges by location when a site changes hands. Bulk updates handle a whole floor at once.
-
People operations
Keep authorization assignments current
See who is assigned to authorize what in Dayforce, add assignments for new team leads, and update a group of assignments when a department reorganizes.
Try asking
- “Update the home address for Priya Nair after her move”
- “List every badge issued for the Toronto office this quarter”
- “Show federal tax records created for new Canadian hires this month”
AI tools
Dayforce tools for your AI agents
310 tools are ready to call through Elaichi's MCP endpoint the moment you connect Dayforce, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 233 of 310 Dayforce tools here. Connect Dayforce and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Dayforce gets you
6 screens from the product, each doing one job for your Dayforce account.
The agent
Ask Dayforce a question, get a real answer.
Employee addresses, tax records and availability, answered in plain language from live Dayforce data.
- addresses
- badges
- tax statuses
- authorization assignments
Ask Elaichi to work across your apps.
Update the home address for Priya Nair after her move
List every badge issued for the Toronto office this quarter
Show federal tax records created for new Canadian hires this month
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Dayforce endpoint for every AI client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
310 Dayforce tools, no custom code needed.
Addresses, badges, tax records and availability, every resource and method listed and ready.
- Dayforce addresses bulk update
- Create a Dayforce address
- List all Dayforce addresses
- Dayforce aus federal taxes bulk update
Toolboxes
Every team gets its own Dayforce toolbox.
Payroll, HR and operations each see only the Dayforce tools their work needs.
- HR
- Payroll
- Operations
- Facilities
Shared connections
Share Dayforce access without sharing a credential.
One person connects Dayforce, teams work through it, nobody else handles the API key.
- Payroll US
- Payroll Canada
- Payroll Australia
- HR
Audit log
Every Dayforce change has a name on it.
When, who, what happened and which record, kept in an append-only log.
- 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 runs Dayforce work end to end.
New addresses are fetched, grouped and drafted into a digest, approved, then posted back to Dayforce.
Dayforce digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch addresses
Dayforce
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
Dayforce
Queued
Collections and dashboards
Dayforce health numbers, refreshed on a schedule.
Four metrics, 14 days of records created and a breakdown by team, no model involved.
Dayforce health
Refreshed 4 minutes ago · every 15 minutes · from the addresses collection
Addresses
1,284 ↓ 12%
Badges
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Addresses created
Last 14 days
By team
Share of activity
Payroll US 34%
Payroll Canada 27%
Payroll Australia 21%
HR 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Dayforce to Claude?
Connect Dayforce in Elaichi by pasting in your Dayforce API key, then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register on the Dayforce side and no client ID or secret to generate. Once added, you sign in to Elaichi as yourself and Dayforce shows up in Claude ready to use.
Does Dayforce work with ChatGPT and Cursor as well as Claude?
Yes. Dayforce is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Nothing is set up separately per client.
What can an AI agent actually do with my Dayforce data?
An agent connected to Dayforce can look up and update employee addresses, create and list federal and state tax records for Canada and Australia, manage badges and authorization assignments, and check a person's availability. It can also handle bulk updates, such as changing tax statuses for a whole group of employees in one go. Short, concrete asks like "list badges for the Toronto office" work better than long paragraphs.
Does connecting Dayforce give the AI access to every employee record?
No. Every request to Dayforce runs as the person who signed in, so the agent sees only the employees, addresses and tax records that person can already see in Dayforce. Elaichi can narrow that access further by team or by action, and it can never widen it beyond what Dayforce already allows.
Can I stop an agent from deleting or changing things in Dayforce?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Dayforce addresses and tax records while blocking creates and bulk updates. A restricted action is never offered to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Dayforce connection when someone leaves?
Offboarding a person in Elaichi ends their access to Dayforce through every client at once. If they connected a shared Dayforce account, that connection keeps working for everyone else on the team. Disconnecting Dayforce once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Dayforce MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Dayforce 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 Dayforce 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.