HRIS
Humaans MCP connector
The Humaans connector brings people records, time away, locations, and bank details into Claude, ChatGPT, Cursor, and any MCP client, so each person can look up, add, and update them within their own Humaans access.
-
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 Humaans to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Humaans once
-
Open Connections, choose Add connection, and pick Humaans.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Humaans API key. One person generates a token in Humaans 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.
Connect Humaans to 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.
Connect Humaans to 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.
Connect Humaans to 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 Humaans 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 Humaans through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
People
Onboard a new hire in one go
Create the person in Humaans, set their location, and add their bank details from the offer paperwork without opening a single form.
-
People
Answer who is out this week
Ask for everyone on time away across a team or location and get the list with dates, so cover can be arranged before Monday.
-
Managers
Log approved leave from a chat
Record a direct report's time away as soon as it is agreed, and correct the dates later if plans change.
-
Payroll
Check bank details before payroll runs
Pull the bank account on file for each employee and spot anyone missing details before the cutoff, rather than chasing them after the run.
-
Operations
Keep office locations current
Add a new office, update an address, or remove a closed site so every person record in Humaans points somewhere real.
-
People
Catch the record up after a change
After a promotion, move, or name change, update the person's details in Humaans in one ask instead of clicking through their profile.
Try asking
- “List everyone on time away in Humaans next week”
- “Who joined Humaans this quarter and in which company”
- “Show pending time away requests for the Engineering team”
AI tools
Humaans tools for your AI agents
165 tools are ready to call through Elaichi's MCP endpoint the moment you connect Humaans, 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 Humaans gets you
6 screens from the product, each doing one job for your Humaans account.
The agent
Ask about people, get real Humaans answers.
Plain language questions read live Humaans people, time away and compensation records.
- people
- companies
- time away
- bank accounts
Ask Elaichi to work across your apps.
List everyone on time away in Humaans next week
Who joined Humaans this quarter and in which company
Show pending time away requests for the Engineering team
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Humaans.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
165 Humaans tools ready without custom code.
People, companies, time away and bank accounts, every resource and method listed.
- List all Humaans people
- Get single Humaans person by ID
- Create a Humaans person
- Update a Humaans person by ID
Toolboxes
Every team gets its own Humaans toolbox.
Curate one toolbox per team so People Ops and Finance see different Humaans tools.
- People Ops
- Finance
- Recruiting
- IT
Shared connections
Teammates use Humaans without seeing credentials.
See who connected each Humaans account and which teams and members it reaches.
- People Ops
- Finance
- Payroll EMEA
- IT
Audit log
Every Humaans call is on the record.
When, who, what happened, type and resource, appended for each person or time away change.
- 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 your Humaans digest.
Fetch Humaans time away, group it, draft a digest, approve, post it back.
Humaans digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch people
Humaans
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
Humaans
Queued
Collections and dashboards
Humaans headcount metrics computed, not requested.
Four metrics, 14 days of people created and a team breakdown, refreshed on schedule.
Humaans health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
People Ops 34%
Finance 27%
Payroll EMEA 21%
IT 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Humaans to Claude?
Two steps. In Elaichi, choose Humaans and paste in an API key from your Humaans account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Humaans is ready to use.
Does Humaans work with ChatGPT and Cursor as well as Claude?
Yes. Once Humaans 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 Humaans once and every client picks it up.
What can an AI agent actually do with my Humaans data?
It can look up any person in Humaans, add a new hire, and update details like title, manager, or start date. It can list who is on time away, record or change leave, keep office locations current, and add or check the bank account on file for an employee. Short, specific asks work best, such as "who in the London office is out next week" rather than a long paragraph.
Does connecting Humaans give the AI access to everyone's records?
No. Every request runs as the person who signed in, so the AI sees exactly what that person can already see in Humaans, and nothing more. Elaichi can narrow that further, for example hiding bank details from a team, but it can never widen access beyond what Humaans itself allows that person.
Can I stop an agent from deleting or changing things in Humaans?
Yes. Restrictions in Elaichi work per action, so you can allow reading people and time away in Humaans while blocking updates, deletions, or anything touching bank accounts. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt, however worded, can reach it.
What happens to a Humaans connection when someone leaves?
Offboarding them in Elaichi ends their access to Humaans through every client at once. If they had shared a Humaans connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Humaans once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Humaans in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.