ClayHR MCP connector
The ClayHR connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up and update employees, org units, job profiles and timesheets in ClayHR, with every person signed in as themselves and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Who reports to Priya Nair in ClayHR?
Working in ClayHR with Elaichi
-
List all ClayHR users
-
Get single ClayHR user by ID
-
ClayHR users search
How to connect ClayHR to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ClayHR 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.
ClayHR 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.
ClayHR 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.
ClayHR 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.
ClayHR 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 ClayHR 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 ClayHR through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ClayHR is logged.
-
HR
Set up a new hire in ClayHR
Create the employee record, set who they report to, fill in the custom fields your organization tracks and upload their photo, all from one request instead of six screens.
-
HR
Record a leave balance for an employee
Add a PTO balance for someone who just joined or changed contract, then confirm the record reads the way it should.
-
Managers
See who reports to whom
Ask for a person's reporting line, the people under them and the org unit they sit in, and get the answer from live ClayHR records.
-
Finance
Check financial status before payroll runs
Pull the financial status for a list of employees and spot anything missing before the payroll cut-off, without opening each profile.
-
IT
Review who holds which ClayHR permissions
List the permissions attached to a user or a group of users and catch access that should have changed with a role change.
-
Operations
Clock in, clock out, fix a timesheet
Clock a shift in or out, review your time allocations for the week and remove a timesheet entry that was logged by mistake.
Try asking
- “Who reports to Priya Nair in ClayHR?”
- “List our org units and the job profiles in each”
- “Show my timesheet allocations for this week”
What connecting ClayHR gets you
6 screens from Elaichi, each doing one job for your ClayHR account.
Ask Elaichi to work across your apps.
Who reports to Priya Nair in ClayHR?
List our org units and the job profiles in each
Show my timesheet allocations for this week
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about employees and timesheets in plain language.
Three starter prompts pull answers from live ClayHR users, org units and timesheets.
Copy the endpoint
AI apps
One endpoint connects ClayHR to every client.
Claude, ChatGPT and Cursor reach ClayHR through one governed endpoint, no SDK, no shared key.
Tool catalog
130 ClayHR tools, ready with no code.
Users, org units, job profiles, custom fields and timesheets, covered without writing a connector.
Toolboxes
Each team gets its own ClayHR toolbox.
HR, Finance and Managers each see a toolbox scoped to the ClayHR work they do.
Shared connections
Teammates use ClayHR without seeing the key.
One person connects ClayHR, shares it with teams, and nobody else handles the API key.
Audit log
Every ClayHR call names who did what.
When, who, what happened, type and resource, logged for every user lookup and timesheet change.
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.
ClayHR digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
ClayHR
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
ClayHR
Queued
Workflows
A schedule starts ClayHR work, a person approves.
Fetch new ClayHR users, group them, draft a digest, approve it, post it back.
ClayHR health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Org units
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
HR Core 34%
Payroll 27%
People Ops 21%
Managers 18%
Collections and dashboards
ClayHR health numbers arrive without asking.
Four metrics, a 14 day chart of users created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ClayHR
All three can connect ClayHR 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 ClayHR tools | Allow or restrict single ClayHR 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 ClayHR 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.
ClayHR tools for your AI agents
130 tools are ready to call through Elaichi's MCP endpoint the moment you connect ClayHR, 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 ClayHR to Claude?
Connect ClayHR in Elaichi first, which asks for the API key from your ClayHR account; there is 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 ClayHR is available in your next conversation.
Does ClayHR work with ChatGPT and Cursor as well as Claude?
Yes. Once ClayHR 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 ClayHR once and every client sees it.
What can an AI agent actually do with my ClayHR data?
With ClayHR connected, an agent can find an employee, read their basic profile, financial status and permissions, see who they report to and which org unit they belong to, and list job profiles and custom fields. It can also create or update an employee, set a reporting line, add a PTO balance, upload a photo, clock in and out, and remove a timesheet entry. Short, concrete asks such as "who reports to Dana in ClayHR" work better than long paragraphs.
Does connecting ClayHR give the AI access to every employee record?
No. Every call to ClayHR runs inside the access of the person who signed in, so an agent sees exactly what that person could see in ClayHR and nothing more. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in ClayHR?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting timesheets or updating employee records for a role or for one person while leaving lookups open. A restricted ClayHR action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a ClayHR connection when someone leaves?
Offboarding a person in Elaichi ends their access to ClayHR through every client at once. A shared ClayHR connection keeps working for everyone else on the team. If you disconnect ClayHR once in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the ClayHR MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ClayHR 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 ClayHR?
Yes. Both let Claude, ChatGPT or Cursor use ClayHR. 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 ClayHR call.
How is Elaichi different from Composio for ClayHR?
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 ClayHR: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ClayHR 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