Dayforce MCP connector
The Dayforce connector brings employee records, schedules, availability, candidate background screening and benefits carrier feed exports to Claude, ChatGPT, Cursor and the Elaichi Agent, with every request running as the signed-in person and recorded in an audit log.
-
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
Catch an employee record up after a change
When someone moves teams, changes manager or gets a new title, ask for the update in plain language and the Dayforce employee record is changed as you, with the change logged.
-
Recruiting
Move a batch of candidates through screening
Update background screening status, adjudication outcome or right to work for a whole group of Dayforce candidates in one ask, instead of opening each candidate one at a time.
-
Operations
Find out who can cover a shift
Ask who is available on Saturday afternoon and see Dayforce availability and schedules for the team, then record new availability when someone lets you know their hours have changed.
-
Benefits
Confirm carrier feed exports went out
Check the ongoing and open enrollment carrier feed exports in Dayforce, including multi carrier feeds, before the carrier calls to ask why an enrollment is missing.
-
People operations
Set up a new hire without retyping
Create the Dayforce employee record from the offer details you already have, then look it up by ID later to confirm the fields landed the way you expected.
-
Talent acquisition
Keep screening packages and billing codes current
Add a new background screening package, billing code or provider status in Dayforce when a vendor changes its offering, and list what already exists before you create a duplicate.
Try asking
- “Who on the warehouse team is available this Saturday afternoon?”
- “Update Priya Shah's manager to Daniel Moore in Dayforce.”
- “Which candidates still have a pending background screening status?”
AI tools
Dayforce tools for your AI agents
100 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.
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 about Dayforce in plain language.
Employees, schedules and candidate screening answered from live Dayforce records, not an export.
- employees
- schedules
- candidates
- carrier feeds
Ask Elaichi to work across your apps.
Who on the warehouse team is available this Saturday afternoon?
Update Priya Shah's manager to Daniel Moore in Dayforce.
Which candidates still have a pending background screening status?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Dayforce in Claude, ChatGPT and Cursor.
One governed endpoint for the whole organization, no SDK and no shared API key.
Copy the endpoint
Tool catalog
100 Dayforce tools, ready without writing code.
Employees, schedules, availability, screening and carrier feeds, every resource and method listed.
- List all Dayforce client metadata
- List all Dayforce background screening billing codes
- Create a Dayforce background screening billing code
- List all Dayforce background screening packages
Toolboxes
Every team gets its own Dayforce toolbox.
Recruiting works candidates, Operations works schedules, HR works employee records, nothing else.
- HR
- Recruiting
- Operations
- Benefits
Shared connections
Share Dayforce without sharing the key.
One person connects Dayforce, teammates work through it and never see a credential.
- HR
- Recruiting
- Operations
- Benefits
Audit log
Every Dayforce change has a name on it.
When, who, what happened and which employee, 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 starts real Dayforce work.
New employees are fetched and grouped, a digest is drafted, approved, then posted back.
Dayforce digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch employees
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 numbers without asking anyone.
Employees created over 14 days, split by team, refreshed on a schedule with no model involved.
Dayforce health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Schedules
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
HR 34%
Recruiting 27%
Operations 21%
Benefits 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Dayforce to Claude?
Connect Dayforce in Elaichi first, which asks for the API key from your Dayforce account, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register in Dayforce and no client ID or secret to generate. Once both steps are done, Claude can work with Dayforce employees, schedules and candidates as you.
Does Dayforce work with ChatGPT and Cursor as well as Claude?
Yes. Once Dayforce is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Dayforce once and every client you use picks it up.
What can an AI agent actually do with my Dayforce data?
With Dayforce connected, an agent can look up an employee, update their record, create a new hire, check who is available and what the schedule looks like, move candidates through background screening in bulk, and review benefits carrier feed exports. Short concrete asks work best, such as who is available Friday evening or update this employee's manager. Anything it does runs as the person who signed in.
Does connecting Dayforce give the AI access to every employee record?
No. Access follows the person who signed in, so an agent working through Dayforce sees only the employees, schedules and candidates that person can already see in Dayforce. Elaichi can narrow that further with restrictions, and it can never widen what Dayforce itself allows.
Can I stop an agent from deleting or changing things in Dayforce?
Yes. Restrictions in Elaichi work per action, so you can allow reading Dayforce employees and schedules while blocking updates, creating employees or bulk screening changes. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Dayforce connection when someone leaves?
Offboarding the person in Elaichi ends their access to Dayforce through every client at once. A Dayforce connection they shared keeps working for everyone else on the team. If you want Dayforce gone entirely, disconnecting it 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.