# Humand MCP connector

The Humand connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or Elaichi's agent read and update Humand employees, groups, posts, documents, and rewards, with every action running under the signed-in person's own access and recorded in an audit log.

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

## Facts

| | |
| --- | --- |
| Application | Humand |
| Category | HRIS |
| AI tools | 105 |
| 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 Humand is connected

- Create a Humand profile for Ana Ruiz starting Monday in Finance
- Deactivate the Humand users who left last week
- Draft a post announcing the new parental leave policy

## Connect Humand in Elaichi

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

1. Open Connections, choose Add connection, and pick Humand.
2. Optionally set Share with, then press Connect.
3. Paste a Humand API key. One person generates a token in Humand 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 Humand tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## Humand 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 Humand 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 Humand 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 Humand through Elaichi

### Set up a new hire before day one

HR. Create the employee's Humand profile, fill in their department, location, and manager, and add them to the right groups so their feed and documents are ready when they log in.

### Deactivate leavers and reactivate returners

HR. When someone leaves, switch off their Humand account the same day. When someone comes back from parental leave or a sabbatical, turn it back on without recreating anything.

### Publish an announcement to the right people

Internal communications. Draft a post or upload a policy document and publish it to a specific segment in Humand, such as one office or one department, instead of the whole company.

### Reset a password and fix profile details

IT helpdesk. Reset a locked-out employee's Humand password, correct a misspelled name or an old job title, and update their profile picture from the same conversation.

### Update hundreds of profiles after a reorg

People operations. Move people to new departments, managers, and locations across many Humand users in one pass, then create the new groups the reorg calls for.

### Keep the recognition store current

Rewards. Add a new product to the Humand rewards store, change its details or retire it, and review the exchanges employees have redeemed this month.

## Elaichi vs Zapier MCP vs Composio for Humand

All three can connect Humand 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 Humand tools | Allow or restrict single Humand 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 Humand 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 Humand to Claude?

In Elaichi, open Humand and paste the API key from your Humand admin settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Humand is available in Claude alongside anything else you have connected.

### Does Humand work with ChatGPT and Cursor as well as Claude?

Yes. 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 Humand once in Elaichi and every client picks it up, so there is nothing to set up again per app.

### What can an AI agent actually do with my Humand data?

With Humand connected, you can ask for an employee's profile, create a new hire, deactivate someone who has left, reset a password, or add people to a group. You can also publish a post or a document, add or update a product in the rewards store, and list the exchanges employees have made. Humand has a large set of actions, so short concrete asks like "deactivate Maria Lopez" work better than long paragraphs.

### Does connecting Humand give the AI access to every employee record?

No. The AI acts as the person who signed in, so it can only see and change what that person can already see and change in Humand. Elaichi can narrow that further with restrictions, and it never widens access beyond what the person already has.

### Can my team share one Humand connection?

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

### Can I stop an agent from deleting or changing things in Humand?

Yes. Restrictions in Elaichi work per action, so you can allow reading Humand profiles and publishing posts while restricting deletion of users or products. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

### What happens to a Humand connection when someone leaves?

Offboarding a person in Elaichi ends their access to Humand through every client at once. A Humand connection shared with the team keeps working for everyone else. If you want to remove Humand entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.

### Does the Humand MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Humand 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 Humand?

Yes. Both let Claude, ChatGPT or Cursor use Humand. 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 Humand call.

### How is Elaichi different from Composio for Humand?

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 Humand: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 105 Humand tools

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

- **List all Humand exchanges** (List). Get all exchanges in Humand. Returns: id, status, statusColor, cost, productId, product, userEmployeeInternalId, createdAt.
- **Create a Humand product** (Create). Create a product in Humand. Returns: id, name, cost, coverPicture, description, category, attachments. Required: name, cost, coverPicture.
- **Update a Humand product by ID** (Update). Edit a Humand product by id. Returns the updated product object including its id. Required: id.
- **Delete a Humand product by ID** (Delete). Delete a Humand product by id. Returns an empty 204 response on success. Required: id.
- **List all Humand users** (List). List Humand users with support for searching and pagination. Returns: id, employeeInternalId, status.
- **Create a Humand user** (Create). Create user in Humand. Returns: id, createdAt, updatedAt, deleted, status, segmentation, relationships, fields. Required: password, employeeInternalId, firstName, lastName.
- **Humand users upsert** (Upsert). Upsert user in Humand. Returns: id, createdAt, updatedAt, deleted, status, segmentation, relationships, fields. Required: password, employeeInternalId, firstName, lastName.
- **Humand users get me** (Get). Get user profile in Humand. Returns: id, createdAt, updatedAt, deleted, status, segmentation, relationships, fields. Get the basic information of the logged user.
- **Humand users upsert alt** (Upsert). Upsert a user in Humand — update an existing user or create a new one if it does not exist. Returns the created or updated user object. Relationships use merge-by-type semantics: sending BOSS entries (or []) updates or clears org-chart bosses and reviewer; sending only REVIEWER entries leaves existing bosses untouched. Set employeeInternalId to null to remove that relationship type. A user cannot…
- **Humand users deactivate** (Deactivate). Deactivate a Humand user by their employee internal id. Returns an empty 204 response on success. Required: employee_internal_id.
- **Humand users reactivate** (Reactivate). Reactivate a deactivated Humand user by their employee internal id. Returns an empty 204 response on success. Required: employee_internal_id.
- **Humand users reset password** (Action). Reset the password for a Humand user identified by their internal employee id. Returns an empty 204 response on success. Required: employee_internal_id.
- **Humand users add segmentations** (Add). Add segmentations to a Humand user by employee internal id. Returns the updated user object including employeeInternalId, status, and segmentations. Required: employee_internal_id, segmentations.
- **Get single Humand user by ID** (Get). Get a single Humand user by employee internal id. Returns the full User object including employeeInternalId, relationships, and segmentations. Required: id.
- **Update a Humand user by ID** (Update). Partially update user in Humand. Returns: id, createdAt, updatedAt, deleted, status, segmentation, relationships, fields. Update an existing user.
- **Delete a Humand user by ID** (Delete). Delete a Humand user by id. Returns an empty 204 response on success. Required: id.
- **Humand users delete alt** (Delete). Delete a Humand user by employee internal id using the POST-based delete endpoint. Returns an empty 204 response on success. Required: employee_internal_id.
- **Humand users update profile fields** (Update). Update user profile fields in Humand. Returns: id, createdAt, updatedAt, deleted, status, segmentation, relationships, fields. Required: employee_internal_id.
- **Humand users update profile picture** (Update). Upload a profile picture for a Humand user identified by their employee internal id. The request body is multipart form data containing the image file. Returns an empty 201 response on success. Required: employee_internal_id.
- **Humand users bulk update** (Update). Update segmentations for a Humand user by employee internal id. Removes previous segmentations belonging to the specified groups and adds the requested segmentations. Returns the updated user object including employeeInternalId. Required: employee_internal_id.
- **Create a Humand document** (Create). Add document for user in Humand. Returns: id, name, source, createdAt, signatureStatus, signatureCoordinates, extension, folderId. Required: employee_internal_id, file. Adds a document whose owner is employeeInternalId.
- **Create a Humand post** (Create). Create post in Humand. Returns: id, body, updatedAt, createdAt, poll, commentCount, attachments, user. Creates a new post given the params.
- **List all Humand segmentations** (List). Get segmentations in Humand. Returns: id, name, items, isEditable, visibility, position. Get all segmentations with items.
- **Humand segmentations create group** (Create). Create a new segmentation group in Humand. Returns the created group including its name, items, and visibility.
- **Humand segmentations add items to group** (Add). Add items to a segmentation group in Humand by group name. Returns the updated segmentation group object including its name, items, and visibility. Required: group_name.
- **Humand segmentations list users** (List). Get users of segmentation items in Humand. Returns: items. Required: segmentationItemIds. Get users of segmentation items.
- **Humand segmentations bulk update** (Update). Update segmentation group in Humand. Returns: id, name, items, isEditable, visibility, position, sharedId. Required: group_name, name, itemNames. Update a segmentation group.
- **Humand files generate signed URL** (Generate). Generate a signed url in Humand. Returns: url, creationUrl. Required: type, fileName, contentType.
- **Humand files generate signed URL temporal** (Generate). Generate a signed url for a temporal file upload in Humand. Returns: bucketUrl, key, policy, Content-Type, x-amz-algorithm, x-amz-date, x-amz-signature. Required: type, fileName, contentType.
- **Create a Humand file** (Create). Create file in Humand. Returns: id, name, type, source, createdAt, updatedAt, uploader, shared. Required: file. Creates a file.
- **Humand files create folder** (Create). Create a folder in Humand. Returns the created folder object including its id and name. Required: name.
- **Delete a Humand file by ID** (Delete). Delete a file in Humand by id. Returns an empty 204 response on success. Required: id.
- **Update a Humand file by ID** (Update). Update a file in Humand by id. Returns an empty 202 Accepted response on success. Required: id.
- **List all Humand acknowledgements** (List). List acknowledgements in Humand. Returns: id, body, points, acknowledger, acknowledged, category, updatedAt, createdAt. List acknowledgements with pagination and sorting.
- **Create a Humand acknowledgement** (Create). Create an acknowledgement in Humand. Returns the created acknowledgement including its id, category, and created_at.
- **Humand acknowledgements adjust points** (Action). Adjust a user's acknowledgement points in Humand. Returns an empty 204 response on success.
- **Create a Humand article** (Create). Create a new article in Humand. Returns: id.
- **Update a Humand article by ID** (Update). Update an existing article in Humand by id. Returns: id. Required: id.
- **Delete a Humand article by ID** (Delete). Delete an article in Humand by id. Returns an empty 204 response on success. Required: id.
- **Humand forms get answers** (Get). Get all answers submitted for a Humand form, including user answers. Returns a paginated list of form answer records with id, created_at, and answers. Required: form_id.
- **Humand time off list balances** (List). List time off balances for employees in Humand. Returns: id.
- **Humand time off list balances by cycle** (List). List time off balances grouped by accrual cycle for employees in Humand. Returns: id.
- **Humand time off list requests** (List). List time off requests submitted by employees in Humand. Returns: id.
- **Humand time off correct balances** (Action). Manually correct or overwrite time off balances for a specific policy type in Humand. Required: policy_type_id.
- **Humand time off update request dates** (Update). Update the dates of an existing time off request in Humand. Returns the updated time off request including its id, state, and dates. Required: request_id.
- **Humand time off bulk create requests** (Create). Bulk-create time off requests for a specific policy in Humand. Returns a job accepted response for tracking the asynchronous bulk creation via the Get Bulk Time Off Requests Creation Job endpoint. Required: policy_id.
- **Humand time off get bulk request job** (Get). Get the status of a bulk time off requests creation job in Humand by bulk_id. Returns: bulk_id. Required: bulk_id.
- **Humand time off bulk update** (Update). Update Time Off Request State in Humand. Returns no content on success. Required: request_id. Update the state of a Time Off Request.
- **Humand groups create post** (Create). Create a post in a Humand group. Returns the created group post object. Required: group_id.
- **Humand time tracking list day summaries** (List). List time tracking day summaries in Humand. Returns a paginated collection of per-day summary records, each containing date, hours (worked, expected, and categorized), time off, holiday, and time slot information.
- ...and 55 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
