Humaans MCP server
Humaans in any MCP client, through Memtro: Humaans does not publish this server. Memtro's Humaans connector reads Humaans 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
Humaans HR: the people directory (work email, status, location, teams, start, probation and leaving dates), job roles with department and manager, time away entries and types, and locations; can book, change or delete time away, record a new job role and adjust a time away allowance. Never dates of birth, addresses, pay or leave reasons.
Reads
humaans_list_peopleThe Humaans directory: name, work email, status (active, offboarded, newHire), location, teams, whether a manager, and start…humaans_get_personOne Humaans person by id, directory fields only.humaans_list_job_rolesJob roles: job title, department, who the role reports to, and when it took effect and ended.humaans_list_time_awayTime away entries (holiday, sickness, working from home, training…) overlapping a window: who, which type, start and end dates and half-days…humaans_list_time_away_typesTime away types and their ids, to read the type_id on time away entries.humaans_list_locationsCompany locations (offices) and their ids, to read the location_id on people.
Acts, when you ask
These change something in Humaans. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
humaans_create_time_awayBooks time away (holiday, sickness, working from elsewhere…) for a person in Humaans.humaans_update_time_awayChanges a Humaans time away entry's dates, half-days, type, note or approval status (approve or decline a pending request).humaans_delete_time_awayPermanently deletes a Humaans time away entry; it cannot be undone and the days return to the allowance.humaans_create_job_roleRecords a new job role for a person in Humaans (title, department, manager) taking effect on a date…humaans_create_time_away_adjustmentAdds days to (or, with a negative amount, removes days from) a person's time away allowance of one type in Humaans, with a reason.
Connect it
First connect Humaans on Dashboard → Connections, then add Memtro to your client once. The Humaans tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
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 Humaans 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 is away this week, and is it holiday or sickness?
- › Who reports to Priya Nair?
- › Whose probation ends in the next month?
- › Book Dan Fletcher's holiday from 22 to 24 December
- › Approve Priya Nair's pending time away request for next Friday
Questions
- Is this an official Humaans MCP server?
- No. It is Memtro's MCP server with Memtro's Humaans connector behind it: the connector reads Humaans through its API with the credentials you connect on Dashboard → Connections, and Humaans 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 Humaans?
- Only when you ask, and only what it has been granted: book time away for a person in Humaans; change the dates, type or approval status of time away in Humaans; delete a time away entry in Humaans (permanent); record a new job role for a person in Humaans; add or remove days from a person's time away allowance in Humaans. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- 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.