Connect your AI tools to live people data

starburst design, abstract graphic element
slack-logo, communication-app
3D geometric shape icon on a dark background, symbolizing design or technology concept, minimalist logo design with cube elements
colorful star logo, modern design icon

People context inside every AI workflow

headphones, chat inquiry

Get access

Already a customer? Get access to HiBob Slackbot HCM

What changes when AI has people context

Make self-service actually useful

HiBob MCP gives employees instant answers inside the tools they already use. With Bob employees can:

  • Ask for leave balances and submit time off
  • Update profile information
  • Understand reporting lines

Accelerate people workflows

HiBob MCP brings HR actions into everyday tools, with Bob governing every workflow.

  • Turn questions into completed actions
  • Reduce chasing and manual handoffs
  • Keep every action connected to Bob

Retain top performers

Bob holds the context. MCP surfaces the risk while you can still act on it.

  • Spot flight risk from real signals like tenure and comp timing
  • Identify at-risk talent with live data.
  • Act in-chat: flag it, brief the manager, start a plan.

People context, inside AI workflows

Connect your AI tools to live people data and workflows from Bob

GDPR emblem in a circular star design, symbolizing data protection and privacy regulations in the EU, GDPR compliance symbol for data privacy
AICPA SOC 2 compliance logo, featuring a circular design with "SOC 2" prominently displayed., AICPA logo, SOC 2 compliance
ISO 27001 certification logo featuring a globe, indicating standards in information security management., ISO, 27001
hipaa, medical-symbol

Frequently asked questions

The HiBob MCP Server is a hosted connector that lets supported AI tools work with live, permissioned people data from Bob. Employees ask in natural language; Bob checks their existing permissions, then returns answers or runs supported HR actions — without copying your full Bob database into the AI tool.

HiBob MCP currently supports ChatGPT, Claude.ai, Claude Desktop, and Cursor. An admin adds the HiBob connector in the AI tool; each employee then signs in with their own Bob account.

Each person connects with their own Bob login. For every request, Bob authenticates the signed-in employee and applies that person’s current Bob permissions — no more, no less. If someone’s access changes or they leave the company, those permissions are enforced immediately.

Bob permissions remain the source of truth: if someone can’t see or do it in Bob, they can’t see or do it through MCP. Some AI tools also let admins block specific tools or require extra confirmation before writes. Turning MCP on in Bob makes it available company-wide; use your AI tool’s admin settings if you need to limit who can use the connector.

Capabilities depend on what’s enabled in your company and what each employee is allowed to do in Bob. At a high level, that can include people data and org context, time off, tasks and approvals, and — where the module is on and permitted — areas such as attendance, performance, goals, learning, hiring, and compensation. Both read and write actions are supported where Bob already allows them.

Yes. Each employee signs in with their own Bob account. Two people can ask the same question and see different results, because each session is scoped to that person’s permissions.

Admins enable Bob MCP in Bob. IT adds the HiBob connector in a supported AI tool. Each employee then opens the connector and signs in with their Bob account. After that, they can use HiBob from chat, with Bob governing every request.

Try prompts like: “What Bob MCP capabilities do I have access to?”, “Who on the Engineering team is out next week?”, “What open tasks are assigned to me?”, or “List name, title, department, and manager for everyone in Product who is currently active.” Responses are generated by the AI tool, so people should review them before acting.

Ready to see Bob AI in Action?