# Humi by Employment Hero MCP connector The Humi by Employment Hero connector lets Claude, ChatGPT, Cursor and the Elaichi Agent look up employees, time off requests and additional incomes, and log hours worked, with each person acting under their own Humi access. Source: https://elaichi.ai/connectors/humi/ ## Facts | | | | --- | --- | | Application | Humi by Employment Hero | | Category | HRIS | | AI tools | 6 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, 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 Humi by Employment Hero is connected - Who is on time off next week in the Toronto office? - List pending time off requests for the support team. - Log eight hours worked today for Priya Shah. ## Connect Humi by Employment Hero in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Humi by Employment Hero. 2. Optionally set Share with, then press Connect. 3. Paste a Humi by Employment Hero API key. One person generates a token in Humi by Employment Hero 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 Humi by Employment Hero tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Humi by Employment Hero 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. ## Humi by Employment Hero 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 today. The plugin directory lives at chatgpt.com/plugins. ## Humi by Employment Hero 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. ## Connect Humi by Employment Hero 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 Only Read is granted by default, which is not enough to call a Humi by Employment Hero tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Humi by Employment Hero through Elaichi ### Answer who is off next week People. Ask which employees have time off requests next week and get the list back in seconds, without opening Humi by Employment Hero and clicking through each person. ### Check a team member's time off history Managers. Pull up one employee's time off requests before a one on one, so the conversation about balance and coverage starts with the facts. ### Review additional incomes before the pay run Payroll. List additional incomes such as bonuses and commissions ahead of payroll and ask the agent to summarize what changed since last period. ### Log hours worked after a shift Operations. Tell the agent who worked and for how long, and it records the time worked in Humi by Employment Hero so nobody types it in twice. ### Pull headcount by department for the forecast Finance. Ask for a count of current employees broken down by department or location and drop the numbers straight into the budget model. ### Find an employee's details fast Office. Look up a single employee by name to get their role, manager and start date when a visitor, courier or new hire asks. ## Frequently asked questions ### How do I connect Humi by Employment Hero to Claude? Connect Humi by Employment Hero in Elaichi first: pick it from the catalog and paste in the API key from your Humi account, which takes about a minute. 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. Claude asks you to sign in to Elaichi, and from then on it can work with Humi by Employment Hero as you. ### Does Humi by Employment Hero work with ChatGPT and Cursor as well as Claude? Yes. Once Humi by Employment Hero 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 Humi by Employment Hero once and every client picks it up. ### What can an AI agent actually do with my Humi by Employment Hero data? An agent connected to Humi by Employment Hero can list employees, look up one employee's details, show time off requests for the whole company or a single person, list additional incomes such as bonuses, and log hours worked for an employee. In practice that means asking who is off next week, checking a team member's leave history, or recording a shift after it ends. Short, concrete asks such as "list pending time off for the support team" work better than long sentences. ### Does connecting Humi by Employment Hero give the AI access to every employee record? No. Every call to Humi by Employment Hero runs under the access of the person who signed in, so a manager sees what that manager can already see in Humi, and an administrator sees what an administrator sees. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Humi by Employment Hero already allows that person. ### Can my team share one Humi by Employment Hero connection? Yes. One person connects Humi by Employment Hero with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup and every logged shift. ### Can I stop an agent from logging hours or changing anything in Humi by Employment Hero? Yes. Restrictions in Elaichi apply per action, so you can allow reading employees and time off requests while blocking the one action that writes to Humi by Employment Hero, logging time worked. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it. ### What happens to a Humi by Employment Hero connection when someone leaves? Offboarding a person in Elaichi ends their access to Humi by Employment Hero through every client at once. If the connection was shared with a team, it keeps working for everyone else, because nobody's access depended on that person's login. If you want Humi by Employment Hero gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ### Does the Humi by Employment Hero MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. Humi by Employment Hero 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. ## All 6 Humi by Employment Hero tools Every tool below is callable through https://api.elaichi.ai/mcp once Humi by Employment Hero is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Humi by Employment Hero employees** (List). List the employees of the Humi company behind the connected token (Humi Partners API, Employee Index). Each record is a JSON:API resource: id, type (employees) and attributes (first/last name, legal names, email, phones, department, position, office, employment_type, start_date, end_date, created_at, updated_at). Deleted employees are not returned. Oldest created_at first; at most 25 per page (use limit and next_cursor). For one employee with manager, salaries or custom fields, use employees.get. Humi labels this API a closed beta; an invalid or revoked token gets a 401 with an empty body. - **Get single Humi by Employment Hero employee by ID** (Get). Get one employee by their Humi employee id, a uuid (Humi Partners API, Employee Show). Returns the whole JSON:API document, not only the record: data (id, type, attributes including reports_to_id, the id of the employee this one reports to), jsonapi and meta. Set include to salaries, custom_attributes or both (comma-separated) to also get data.relationships and a top-level included array: salary records (name, rate, frequency, is_primary, effective_at, ends_at) and custom field values (name, value, type, field_group). Deleted employees are not returned. - **List all Humi by Employment Hero time off requests** (List). List APPROVED time off requests company-wide that overlap a date range (Humi Partners API, Time Off Index). Required: date_range_start and date_range_end (YYYY-MM-DD), sent as dateRange[start] and dateRange[end]. A request matches when its start_at, end_at or any day between falls in the range. Pending and denied requests are never returned. Records: id, type (timeOffRequest), attributes (employee_id, type, start_at, end_at, status, description, total_amount_days, total_amount_hours, created_at, updated_at). Newest updated_at first; at most 25 per page. Re-send both dates with next_cursor. - **List all Humi by Employment Hero employee time off requests** (List). List one employee's APPROVED time off requests that overlap a date range (Humi Partners API, Time Off Show). Required: employee_id (Humi employee uuid), date_range_start and date_range_end (YYYY-MM-DD, sent as dateRange[start] and dateRange[end]). Same matching rule, records (id, type, attributes with employee_id, start_at, end_at, status, day and hour totals, timestamps), order (newest updated_at first) and paging (at most 25 per page) as time_off_requests.list. Re-send all three inputs with next_cursor. - **List all Humi by Employment Hero additional incomes** (List). List the company's payroll additional income types (Humi Partners API, Additional Incomes Index). Humi returns the same standard list for every company, but the ids are company-specific: use them as the additional income ids in employee_time_worked.create. Records: id, type (additionalIncome), attributes.name (machine-readable, e.g. holiday_pay) and attributes.displayName. Takes no query parameters; not paginated. - **Create a Humi by Employment Hero employee time worked** (Create). Record time worked for ONE employee on Humi's open payrolls (Humi Partners API, Employee Time Worked). WARNING: reset defaults to true, and Humi says true "will destroy all previous time worked entries on open payrolls". Send reset=false unless you mean to replace them; send an entry's id to update it. Additional income ids come from additional_incomes.list. Humi answers 202 Accepted with employee_id and time_worked (id, start_time, end_time, line_items with rate_id, name, hours, overtime_hours, amount). Amounts are calculated out-of-band (eventually consistent) and may not be final yet.