Is this an official HiBob MCP server?

No. It is Memtro's MCP server with Memtro's HiBob connector behind it: the connector reads HiBob through its API with the credentials you connect on Dashboard → Connections, and HiBob publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in HiBob?

Not yet. Today every HiBob tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · People and HR

HiBob MCP server

HiBob in any MCP client, through Memtro: HiBob does not publish this server. Memtro's HiBob connector reads HiBob through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only HR directory from HiBob: who works here in which role, department and site, who reports to whom, start dates, who is out of office, and recent starters and leavers. Never reads salary or personal data.

Reads

hibob_peopleFind people in HiBob by name, email, title or department, optionally narrowed by department, site or manager.
hibob_personOne employee by HiBob id, work email or full name: role, department, site, start date, status, manager chain, direct reports, and…
hibob_orgOrg shape: departments and sites with headcounts (and configured values with nobody in them), plus, for a manager…
hibob_whos_outWho is out of the office in a date range (default today through the next 7 days): person, leave type (e.g. Holiday, Sick) and dates…
hibob_changesPeople changes in a window (default the last 30 days): starters (by start date) and leavers (by termination date); with an employee…

Connect it

First connect HiBob on Dashboard → Connections, then add Memtro to your client once. The HiBob tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared HiBob connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who does Priya report to and who is on her team?
› How big is Engineering by site?
› Who is out next week?
› Who started in the last month?

Questions

Is this an official HiBob MCP server?: No. It is Memtro's MCP server with Memtro's HiBob connector behind it: the connector reads HiBob through its API with the credentials you connect on Dashboard → Connections, and HiBob publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in HiBob?: Not yet. Today every HiBob tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.