
List HiBob documents for employee. Returns document metadata including name, upload date, folder, and tags. Does not return document contents - use download URL if provided.
Get one of a HiBob employee's documents by ID, including its time-limited download link. Set returndownloadurl=true to hand the file off for download instead of returning metadata. Use listemployeedocuments to find document IDs. HiBob has no single-document endpoint, so this reads the employee's document list and picks out the one you asked for.
Upload document to HiBob employee folder from URL. Specify folder_type ('shared' or 'confidential'). Optionally add tags. Returns uploaded document ID.
Delete HiBob document from employee folder. Requires documentid from listemployeedocuments and foldertype ('shared' or 'confidential'). Document deletion is permanent and cannot be undone.
Get HiBob document folder metadata. Returns available folder types and IDs. Use to understand document organization before uploading.
Search HiBob employees. Filter by ID or email only (API limitation - use root.id or root.email with equals operator). Returns paginated employee records with work info. Use listemployeefields first to see available field IDs for the fields parameter.
Get detailed HiBob employee by ID. Returns work info, about section, and custom fields. Specify field IDs to limit response size. Use listemployeefields to see all available fields.
Create new HiBob employee. Required: email, firstName, surname, site (must be valid list item), startDate. Returns created employee. Use getnamedlist with 'site' to find valid site values first.
Update HiBob employee fields. Pass field paths and values (e.g., 'work.title': 'Senior Engineer'). Use listemployeefields to find valid field paths. Returns updated employee record.
Terminate HiBob employee with termination date and optional reason. Sets employee status to terminated and records last day of employment. Cannot be undone via API.
Revoke HiBob employee's system access. Employee record remains but they cannot log in. Use for immediate access removal without full termination.
Get metadata for all HiBob employee fields. Returns paginated field IDs, names, types, and categories. Use field IDs in searchemployees and getemployee. No special permissions required.
Get items from HiBob named list (departments, sites, divisions, etc.). Returns paginated list items with IDs and names. Use list_name parameter with values like 'department', 'site', 'division', 'employmentType'.
Add new item to HiBob named list (e.g., add new department or site). Returns updated list with new item. Use getnamedlist first to see existing items and avoid duplicates.
Search HiBob goals with filters. Filter by ownerid, goaltypeid, cycleid, or status. Returns paginated results. Use getgoalmetadata for valid goaltypeid and cycle_id values.
Get HiBob goal metadata (types or cycles). Set metadata_type to 'goal-types' for goal types or 'cycles' for goal cycles. Use returned IDs when creating goals.
Get HiBob company employee field configuration. Returns all configured employee fields with IDs, types, categories, and whether they track history. Use for understanding data model.
List all HiBob company reports. Returns paginated report IDs, names, descriptions, and categories. Use report ID with downloadreport or downloadreport_async.
Download HiBob report synchronously (for small/medium reports). Returns report data as CSV or JSON string. For large reports, use downloadreportasync instead.
Download HiBob report asynchronously (for large reports). Returns download_url with the report location. Use WebFetch or similar to download the file from the URL.
List all open HiBob tasks across the organization. Returns paginated task title, description, assignee, due date, and workflow info. Use for task management and onboarding tracking.
Get HiBob tasks for specific employee. Filter by task_status ('open' or 'closed'). Returns paginated tasks assigned to or about the employee including onboarding tasks.
Mark HiBob task as complete. Provide taskid from listtasks or getemployeetasks. Returns count of tasks updated. Tasks cannot be uncompleted via API.
Submit HiBob time off request. Supports 7 request types (days, hours, etc.) via requestrangetype. Required: employeeid, policytype, startdate, enddate. Use listpolicytypes to find valid policy types.
Get HiBob time off request details by request ID and employee ID. Returns full request including status, dates, policy type, and approver info.
Cancel pending HiBob time off request. Only pending requests can be canceled. Returns canceled request with updated status. Use gettimeoff_request to verify status before canceling.
Get HiBob employee time off balance. Returns available, used, and pending balances by policy type. Optionally filter by policy_type or calculate as of specific date.
Adjust HiBob employee time off balance (admin operation). Add or subtract days/hours. Positive values add balance, negative subtract. Provide reason for audit trail.
List all HiBob time off policy types (Vacation, Sick, etc.). Returns policy type codes to use in submittimeoff_request. No parameters needed.
List HiBob time off policies. Returns policy details including accrual settings. Optionally filter by policy_type.
Get HiBob who's out calendar for date range. Returns paginated list of employees with approved time off. Use for coverage planning and absence visibility. Set include_pending=true to see pending requests.
Get HiBob employees out today. Quick view of current absences. Set include_pending=true to include pending requests.
Get HiBob time off request changes since timestamp. Track approvals, rejections, cancellations. Use ISO 8601 timestamp for 'since' parameter. Useful for syncing with external systems.
Validate HiBob credentials. Verifies credentials during setup.

In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}It's an MCP server that connects your agents to HiBob via tools. Your agents can invoke these tools to search and retrieve employee records, manage time off requests, track task completion, generate workforce reports, and more.
HiBob offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.
The use cases naturally depend on the agent you've built, but here are a few common ones:
create_employee</code> to provision the HiBob record, then calls <code class="blog_inline-code">list_tasks</code> to surface pending onboarding tasks and routes them to the right team members via Slackget_whos_out</code> to check which employees are out of office, cross-references team rosters, and posts a structured coverage summary to a manager Slack channel so the team can plan without logging into HiBobdownload_report</code> for headcount and turnover data, formats the output into a structured summary, and posts it to a leadership channel so stakeholders have current workforce metrics without manual exportsterminate_employee</code> to initiate the offboarding process in HiBob and calls <code class="blog_inline-code">list_employee_documents</code> to surface any outstanding documents the people team needs to collectHere are some of the most commonly used tools:
<code class="blog_inline-code">search_employees</code> queries the HiBob employee directory by name, department, or other fields and returns matching records. Use this when an agent needs to look up a specific person or build a filtered list before taking an action<code class="blog_inline-code">get_employee</code> retrieves the full profile for a specified employee, including personal details, role, and employment status. Call this when an agent needs complete employee context before updating a record or routing a request<code class="blog_inline-code">create_employee</code> adds a new employee record to HiBob with the provided field values. Useful for agents that automate onboarding by syncing new hire data from an ATS or HRIS into HiBob without manual entry<code class="blog_inline-code">submit_time_off_request</code> files a time off request in HiBob on behalf of a specified employee. Good for agents that handle time off workflows triggered by a form submission or a calendar event in another system<code class="blog_inline-code">get_whos_out</code> returns a list of employees currently out of office based on approved time off records. Helpful when an agent needs to assess coverage, route work to available team members, or generate a daily absence report<code class="blog_inline-code">download_report</code> generates and retrieves a HiBob workforce report by report ID. Use this when an agent needs structured headcount, turnover, or compensation data to deliver to a stakeholder or feed into a downstream analytics toolHere is what makes Merge Agent Handler's HiBob MCP server a stronger choice than building or using an alternative:
You can take the following steps:
1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).
2. Create a new Tool Pack, then find and enable the HiBob connector. Choose which tools to include: enable read tools like <code class="blog_inline-code">search_employees</code> and <code class="blog_inline-code">get_whos_out</code> for reporting use cases, or add write tools like <code class="blog_inline-code">create_employee</code> and <code class="blog_inline-code">terminate_employee</code> if your agent needs to manage employee lifecycle events.
3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.
4. From the Registered User detail page, authenticate HiBob by completing the credential flow. Merge stores and manages the credentials going forward.
5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.
6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your HiBob tools are now accessible through that endpoint.
Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to HiBob without bypassing IT governance.
Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity.
IT also provisions access by role or group via SCIM. An HR business partner, for example, gets HiBob access to manage employee records and lifecycle events, Greenhouse to cross-reference recruiting pipelines, and Slack to coordinate with managers on onboarding tasks; while a people operations manager gets HiBob access to track workforce metrics and time off, Google Sheets to report on headcount data, and BambooHR to reconcile HR records across systems.
Every tool call an employee's AI makes to HiBob is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now