Connect your AI Agents to HiBob in minutes

What is a HiBob MCP?

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.

How can I use the HiBob MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Onboarding task automation: When a new hire is created in an ATS like Greenhouse, an agent calls <code class="blog_inline-code">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 Slack

• Daily coverage summary: Each morning, an agent calls <code class="blog_inline-code">get_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 HiBob

• Workforce reporting digest: On a weekly schedule, an agent calls <code class="blog_inline-code">download_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 exports

• Offboarding record update: When an employee departure is confirmed in a ticketing system, an agent calls <code class="blog_inline-code">terminate_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 collect

What are popular tools for HiBob's MCP server?

Here 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 tool

What makes Merge Agent Handler's HiBob MCP server better than alternative HiBob MCP servers?

Here is what makes Merge Agent Handler's HiBob MCP server a stronger choice than building or using an alternative:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For HiBob, this means you can prevent salary data, personal identifiers, employment status, and document contents from being exposed even when the agent has broad read access to employee records

• Managed authentication and credentials: Merge stores and refreshes HiBob credentials on your behalf. You never expose service user tokens to an agent or handle re-authentication when credentials rotate

• Real-time observability and audit trail: Every tool call made against HiBob is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly which employee records an agent read, updated, or terminated without adding any instrumentation to your own infrastructure

• Tool Packs and controlled access: Tool Packs let you bundle specific HiBob tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's HiBob MCP server?

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.