Claude + HiBob: What the Integration Can (and Can't) Do in 2026
Yes — HiBob (Bob) ships its own official MCP server, so Claude can actually reach your people data in 2026. HiBob released a hosted MCP server in beta (announced April 28, 2026), which means Claude Desktop, Claude Code, Cursor, and VS Code can connect over a URL and read employees, time off, and tasks in Bob using a service-user token. There’s no Anthropic Connectors Directory entry for HiBob, but you don’t need one: the vendor built the bridge, and the underlying Bob API covers the rest.
Here’s each route, when to pick it, and what to use when you want HiBob work that happens without you at the keyboard.
Route 1: HiBob’s official MCP server (beta)
This is the one to reach for first. HiBob hosts a remote MCP server at https://api.hibob.com/ai-mcp-public/mcp/public, and any client that can connect to an MCP server over a URL — Claude Desktop, Claude Code, Cursor, VS Code, Microsoft Copilot Studio — can use it.
What it exposes today, per HiBob’s MCP docs:
- People — find employees, read (and update) employee records, traverse the org.
- Time off — see who’s out, check balances, submit time-off requests.
- Tasks — view an employee’s onboarding and offboarding tasks.
Authentication is a Bob service user: you create one in Settings → Integrations → Service Users, grant it the permissions you want the agent to inherit, and pass the Base64-encoded serviceUserId:serviceUserToken credential to your client. The MCP server can only ever do what that service user is allowed to do — so scope it tightly. It’s beta, so expect the tool list and auth (HiBob is layering in OAuth user-based access) to keep shifting.
Setup in Claude Desktop is the standard remote-MCP flow: add the server URL and your encoded token to your MCP config, restart, and Claude can answer “who’s on PTO next week?” against live Bob data.
Route 2: A self-hosted / community MCP wrapper
If you want tighter control over exactly which endpoints the agent can touch, community wrappers exist — you’ll find HiBob MCP servers listed on directories like LobeHub — that run locally and call the Bob API themselves. They typically authenticate with the same building blocks (HIBOB_SERVICE_ID and a service-user token) and expose a narrower toolset, such as employee search via POST /people/search and recursive org-hierarchy traversal.
Because these are self-hosted, verify the source before pointing it at real HR data, and keep the service user read-only unless you genuinely need writes. This route makes sense when you want to run the server inside your own network or trim it to just the two or three tools you trust an agent with. For most people, the official beta server (Route 1) is simpler and better supported.
Route 3: The Bob API directly (Claude Code or a custom script)
Under both MCP routes sits HiBob’s REST API. It uses HTTP Basic Auth with the same service-user credentials, and covers employee data, time off, attendance, tasks, and org structure — plus webhooks for events like time_off.request.approved. Note that Bob keys everything on its internal employee ID, not email, so most lookups start with a /people/search.
If you’re comfortable in Claude Code, you can skip MCP entirely and let Claude write and run a script against the API — useful for a one-off export, a bulk reconciliation, or wiring a webhook. It’s the most flexible route and the most hands-on: you own the auth handling and the code.
(Worth knowing: HiBob also has its own in-product AI — Bob AI — for surfacing people insights inside the platform. That’s separate from letting Claude reach your Bob data, which is what the MCP server and API are for.)
The limits that actually matter
The MCP server is a real, meaningful integration — but be clear-eyed about the boundaries:
- It’s beta. Tools, auth, and the URL can change; don’t build anything mission-critical on it without a fallback.
- No event triggers. Claude’s scheduled tasks run on a clock, never on something happening. Claude won’t notice a new hire lands in Bob and act on it — you ask, or you wait for the next run.
- Scheduled, not event-driven. “Every Monday, list who’s out this week” works as a scheduled task, and it runs remotely. “The moment someone is added to Bob” does not.
- claude.ai on the web can’t reach a local/desktop-only setup. Route 1’s remote server works in supported clients; Route 2/3 local setups don’t reach the web app.
- Scoped to the service user. It reads and acts only as far as that user’s permissions allow — by design.
Claude + HiBob is excellent for asking questions and doing on-the-spot HR admin in a chat. It’s not built for HR work that has to happen the moment something changes in Bob.
If you want HiBob work that runs on its own: Carly
Carly reaches HiBob through your own Bob service-user token (paste it on the integrations page) — one of 200+ native integrations plus anything with an API. Instead of answering in a chat, it runs in the cloud on triggers:
- When a new hire is added in Bob, Carly kicks off the onboarding checklist — creates tasks, emails the manager their to-dos, and pings IT to provision accounts.
- When a time-off request is approved, Carly notifies the team, updates the shared calendar, and flags any coverage gaps for that week.
- Every Monday morning, Carly pulls who’s out from Bob and sends managers a plain-English “out this week” digest before standup.
No-code setup. You don’t write config files or scripts. Describe the workflow in plain English and Carly interviews you to fill in the details, then builds it.
Actually sends. Carly sends real email through Gmail and Outlook — not draft-only.
Connects to anything. 200+ native integrations, plus any tool with an API via your own key, so a Bob event can trigger a Slack message, a task in your PM tool, or a row in your spreadsheet.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude + HiBob | Carly | |
|---|---|---|
| Read & search Bob (people, time off, tasks) | Yes, via official MCP server | Yes, via your service-user token |
| Act inside a session you start | Yes | Yes |
| Acts on triggers (new hire, PTO approved) | No | Yes |
| Runs on a schedule (Monday digest) | No | Yes |
| Runs unattended | Scheduled tasks only | Yes (events + schedules) |
| Sends email as part of the flow | Draft-only | Yes (Gmail + Outlook) |
| Connects to your wider stack | One app per session | 200+ apps + any API |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best way to ask questions and do hands-on HR admin against Bob in a chat. Carly is the way to make that HR work happen on its own — on triggers, on a schedule, without your laptop open.
Frequently Asked Questions
Does Claude work with HiBob?
Yes. HiBob ships an official MCP server (in beta as of 2026) that connects to Claude Desktop, Claude Code, Cursor, and VS Code. Once you add the server URL and a service-user token, Claude can read employees, time off, and tasks in Bob.
Is there an official HiBob MCP server?
Yes — HiBob released a hosted MCP server in beta, announced April 28, 2026, at https://api.hibob.com/ai-mcp-public/mcp/public. It authenticates with a Bob service user and exposes People, Time off, and Tasks tools. Because it’s beta, expect the toolset and auth to keep evolving.
Can claude.ai on the web access HiBob?
The official remote MCP server works in supported desktop and code clients; a self-hosted or local MCP setup won’t be reachable from the claude.ai web app. Either way, Claude only acts when you ask or on a schedule you set — there are no event triggers.
Can Claude onboard a new hire in HiBob automatically?
Not on its own — MCP tools run when you prompt them or when a scheduled task does, so Claude can’t catch a new hire the moment they’re added. For automatic onboarding (create tasks, email the manager, notify IT the moment someone is added), you need a service that runs on triggers, like Carly.
More: Claude connectors · Claude vs Carly · Can Claude send emails · AI agents for HR & people ops · Claude + Rippling · Claude + BambooHR · Best Gusto integrations
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
