Integration

HR Cloud integration

HR Cloud is an HR platform (core HR, onboarding, offboarding, benefits). Its Core HR API lets you list, read, create and update employees, applicants, departments, divisions, positions (job titles), work locations and employment statuses, and list, read and create plain tasks about employees. Lists page with page and pageSize and take a field filter (eq, contains, startswith, gt and more) and a sort. Employees and applicants are personal data: names, emails, phones and addresses, and for employees also date of birth, gender, ethnicity, veteran status, salary and bonus; social security and international tax ids are not returned. Left out: employee attachments, pictures and forms, upsert, updates by another identifier field, field mapping and bulk writes, task updates, and the leave request, time off, salary, bonus and history objects. Authentication is the Key and Secret of an HR Cloud service account (System Settings, General, Service Accounts), sent as the Customer_Key and Customer_Secret headers.

Connect HR Cloud How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in HR Cloud.Built from the 31 HR Cloud tools below, on the connection you add once.

What you can do with HR Cloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

X applicant, 4 operations

create_applicantCreate applicantPOSTCreates an applicant with first and last name, email and the Id of an applicant status (see xApplicantStatusLookup in list_applicants); phone, address and job Id are optional.
get_applicantGet applicantGETReturns one applicant by Id: name, email, address, applied and last-updated dates, applicant status (title and type), job, and resume and cover letter file names. Personal data.
list_applicantsList applicantsGETLists applicants (name, email, address, applied and availability dates, applicant status, job applied to, resume and cover letter file names), with page, pageSize, filter and sort. Personal data.
update_applicantUpdate applicantPUTUpdates an applicant by Id (sent in the body), for example to move it to another applicant status; only the fields sent change. Returns the updated applicant.

X department, 4 operations

create_departmentCreate departmentPOSTCreates a department with a code, a name and a record status (Active or Inactive).
get_departmentGet departmentGETReturns one department by Id: code, name and record status (Active or Inactive).
list_departmentsList departmentsGETLists departments (Id, code, name, Active or Inactive), with page, pageSize, filter, sort and select. A department Id goes in xDepartmentLookup when creating or updating an employee.
update_departmentUpdate departmentPUTUpdates a department by Id (sent in the body): code, name or record status; fields not sent keep their value. Returns the updated department.

X division, 4 operations

create_divisionCreate divisionPOSTCreates a division with a code, a name and a record status (Active or Inactive).
get_divisionGet divisionGETReturns one division by Id: code, name and record status (Active or Inactive).
list_divisionsList divisionsGETLists divisions (Id, code, name, Active or Inactive), with page, pageSize, filter, sort and select. A division Id goes in xDivisionLookup of an employee.
update_divisionUpdate divisionPUTUpdates a division by Id (sent in the body): code, name or record status; fields not sent keep their value. Returns the updated division.

X employee, 4 operations

create_employeeCreate employeePOSTCreates an employee and returns it (personal data, as get_employee). Required: first, last and full name, work email, unique employee number, record status, start date, and the Ids of a department, employment status, location and position.
get_employeeGet employeeGETReturns one employee by Id. Personal data: names, emails, phones, address, date of birth, gender, ethnicity, veteran status, education, salary and bonus, plus employee number, status, dates, department, division, location, position and manager.
list_employeesList employeesGETLists employees (page, pageSize, filter, sort). Personal data: names, emails, phones, address, date of birth, gender, ethnicity, veteran status, education, salary and bonus; also number, status, dates, department, position, manager.
update_employeeUpdate employeePUTUpdates an employee by Id (sent in the body): only the fields sent change, the others keep their value. Salary and bonus cannot be changed this way. Returns the updated employee, with the personal data get_employee returns.

X employment status, 4 operations

create_employment_statusCreate employment statusPOSTCreates an employment status with a name (xType, for example Contractor) and a record status (Active or Inactive).
get_employment_statusGet employment statusGETReturns one employment status by Id: its name (xType) and record status.
list_employment_statusesList employment statusesGETLists employment statuses (Id, name such as Active or Terminated, record status), with page, pageSize, filter, sort and select. A status Id goes in xEmploymentStatusLookup of an employee.
update_employment_statusUpdate employment statusPUTUpdates a employment status by Id (sent in the body): name (xType) or record status; fields not sent keep their value. Returns the updated employment status.

X location, 4 operations

create_locationCreate locationPOSTCreates a work location with a code, a name and a record status (Active or Inactive); description and address are optional. Returns the new location.
get_locationGet locationGETReturns one work location by Id: code, name, description, address and record status.
list_locationsList locationsGETLists work locations (Id, code, name, description, address, Active or Inactive), with page, pageSize, filter, sort and select. A location Id goes in xLocationLookup of an employee.
update_locationUpdate locationPUTUpdates a location by Id (sent in the body): code, name, description, address or record status; fields not sent keep their value. Returns the updated location.

X position, 4 operations

create_positionCreate positionPOSTCreates a position (job title) with a code, a title and a record status (Active or Inactive); a description is optional.
get_positionGet positionGETReturns one position (job title) by Id: code, title, description and record status.
list_positionsList positionsGETLists positions, the job titles employees hold (Id, code, title, description, Active or Inactive), with page, pageSize, filter, sort and select. A position Id goes in xPositionLookup.
update_positionUpdate positionPUTUpdates a position by Id (sent in the body): code, title, description or record status; fields not sent keep their value. Returns the updated position.

X task, 2 operations

get_taskGet taskGETReturns one task by Id: title, comment, type, status, approval status, assignee, due date, related employee, application, employee group, and who created, updated and completed it.
list_tasksList tasksGETLists tasks (title, comment, type, status, approval, assignee, due date, employee concerned, application, creator), with page, pageSize, filter, sort and select.

Portal, 1 operation

create_taskCreate taskPOSTCreates a plain task about employees (relatedToEmployeeIds) in coreHr, onboard, benefits or offboard, assigned by assigneeType. Give fixedDueDate for coreHr or benefits, relativeDueDate for onboard or offboard.

Use HR Cloud from Claude Code, Cursor or Codex

Connect HR Cloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its HR Cloud operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect HR Cloud

Create your workspace
Sign up free. Nothing to install.
Connect HR Cloud once
Add your HR Cloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.