# 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.

Source: https://elaichi.ai/connectors/clayhr/

## Facts

| | |
| --- | --- |
| Application | ClayHR |
| Category | HRIS |
| AI tools | 130 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ClayHR is connected

- Who reports to Priya Nair in ClayHR?
- List our org units and the job profiles in each
- Show my timesheet allocations for this week

## Connect ClayHR in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ClayHR.
2. Optionally set Share with, then press Connect.
3. Paste a ClayHR API key. One person generates a token in ClayHR and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ClayHR tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ClayHR MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## ClayHR MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a ClayHR tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ClayHR through Elaichi

### Set up a new hire in ClayHR

HR. 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.

### Record a leave balance for an employee

HR. Add a PTO balance for someone who just joined or changed contract, then confirm the record reads the way it should.

### See who reports to whom

Managers. 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.

### Check financial status before payroll runs

Finance. Pull the financial status for a list of employees and spot anything missing before the payroll cut-off, without opening each profile.

### Review who holds which ClayHR permissions

IT. List the permissions attached to a user or a group of users and catch access that should have changed with a role change.

### Clock in, clock out, fix a timesheet

Operations. Clock a shift in or out, review your time allocations for the week and remove a timesheet entry that was logged by mistake.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one ClayHR connection?

Yes. One person connects ClayHR with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every ClayHR call.

### 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.

## All 130 ClayHR tools

Every tool below is callable through https://api.elaichi.ai/mcp once ClayHR is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all ClayHR users** (List). Retrieve all users details.
- **Get single ClayHR user by ID** (Get). Retrieve user details. Required: id.
- **Create a ClayHR user** (Create). Create user. Required: firstName, email.
- **ClayHR users upsert** (Upsert). Create or Update user. Creates a user, or updates the user if a match is found. The same call can also save addresses, education, employment history, contacts, compensation, custom field values and rep… Required: email, firstName.
- **ClayHR users search** (Search). Retrieve a user or list of users.
- **ClayHR users list resources** (List). Retrieve users.
- **ClayHR users get basic** (Get). Retrieve user basic information. Required: userID.
- **ClayHR users get financial status** (Get). Retrieve user financial status.
- **ClayHR users get permissions** (Get). Retrieve user permissions and menu configurations.
- **ClayHR users list basic** (List). Retrieve basic user details.
- **ClayHR users add reports to** (Add). Add reports to. Required: userID.
- **ClayHR users save custom field values** (Action). Save Custom Field values.
- **Update a ClayHR user by ID** (Update). Update user. Required: id.
- **ClayHR users upload picture** (Upload). Upload user profile. Required: file, userid.
- **List all ClayHR orgunits** (List). Retrieve org units.
- **Create a ClayHR orgunit** (Create). Create new org unit. Required: name, description.
- **List all ClayHR customfields** (List). Get Custom Fields.
- **Get single ClayHR customfield by ID** (Get). Retrieve a single custom field definition by its ID. Required: id.
- **List all ClayHR jobprofiles** (List). Retrieve job profiles. Required: status.
- **Create a ClayHR pto balance** (Create). Add PTO balance. Required: userId, ptoPolicyId, balance.
- **ClayHR timesheets clock in** (Action). Clock in. Allows to clock in.
- **ClayHR timesheets clock out** (Action). Clock out. Allows user to clock out.
- **Delete a ClayHR timesheet by ID** (Delete). Delete a timesheet. Deletes a timesheet by Timesheet ID. Required: id.
- **ClayHR timesheets list my allocations** (List). Retrieve my active allocations. Retrieve list of active allocations of user.
- **ClayHR timesheets list timecards** (List). Retrieve timecards by Timesheet ID. Retrieve a list of timecards. Required: startDate, endDate.
- **ClayHR timesheets list preferences** (List). Retrieve my timesheet preferences. Retrieve list of timesheet preferences based in cid.
- **List all ClayHR timesheets** (List). Retrieve timesheets by User ID. Retrieve a list of timesheets.
- **Get single ClayHR timesheet by ID** (Get). Retrieve a timesheet by timesheet ID. Required: id.
- **ClayHR timesheets get details** (Get). Retrieve timesheet details by Timesheet ID. Required: timeSheetId.
- **ClayHR timesheets save** (Action). Create/Update a timesheet. Creates a new timesheet and update existing timesheet. Required: date, projectId, elapsedTime.
- **ClayHR timesheets update status** (Update). Update timesheet status by Timesheet ID. Update the timesheet status (submit, approve, reject) corresponding to supplied Timesheet ID. Required: timesheetId, status.
- **ClayHR candidates create from resume** (Create). Create a candidate from pdf resume. Required: file.
- **Create a ClayHR candidate** (Create). Create new candidate.
- **List all ClayHR candidates** (List). Retrieve candidates.
- **ClayHR candidates list basic** (List). Retrieve candidates with basic details.
- **Get single ClayHR candidate by ID** (Get). Retrieve the candidate detail by recruitid. Required: id.
- **Create a ClayHR expense item** (Create). Create expense item. Required: amount, currencyCode, date, remarks, userId, expenseItemId, expenseTypeId.
- **Delete a ClayHR expense item by ID** (Delete). Delete expense item. Required: id.
- **Update a ClayHR expense item by ID** (Update). Edit expense item. Required: amount, currencyCode, date, remarks, userId, id, expenseTypeId.
- **Create a ClayHR expense report** (Create). Create expense report. Required: name.
- **Get single ClayHR expense report by ID** (Get). Retrieve expense report details. Retrieve the details of expense report. Required: id.
- **Delete a ClayHR expense report by ID** (Delete). Delete expense report. Required: id.
- **List all ClayHR expense reports** (List). Retrieve expense reports. Retrieve expense reports with User ID.
- **ClayHR expense reports submit** (Action). Submit expense report. Required: expenseReportId, status.
- **Create a ClayHR performance review** (Create). Create Performance Review. Required: userId, templateId.
- **ClayHR performance reviews list completed** (List). Retrieve Completed Performance Reviews. Required: targetUserId.
- **List all ClayHR performance reviews** (List). Retrieve Performance Reviews.
- **ClayHR performance reviews bulk launch** (Action). Launch Performance Reviews In Bulk.
- **Create a ClayHR skill** (Create). Create a new skill. Required: description, skillCode.
- **List all ClayHR skills** (List). Retrieve skills.
- ...and 80 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
