The Darwinbox MCP server lets Claude work in the Darwinbox HR platform as the signed-in employee. Employees can check balances, apply for leave or work from home, file expenses and view payslips. Recruiters can search candidates, schedule interviews and move people through the pipeline. Each call is limited to what that person can already do in Darwinbox.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
Admin setup comes first. No assigned tools means only a placeholder tool.
Client ID required. Darwinbox issues OAuth clients; there is no self-serve registration.
Messages reach real people. Candidate emails, reminders and pre-offers go out under your Darwinbox identity.
Some deletes are permanent. Darwinbox describes candidate deletion as permanent.
Sensitive personal data. Payslips and candidate data are returned to the chat; your organisation's own data policies apply.
Not HR or legal advice. Answers reflect Darwinbox records and policies, not professional advice.
Per-call limits. Darwinbox states 5 files per call, 10 MB per file and a 120-second upstream timeout.
No schemas read live. Names come from Anthropic's directory; effects come from Darwinbox's published reference.
Frequently asked questions
Why do I only see one Darwinbox tool called no tools or agents available?
Because your administrator has not assigned you any tools yet. Darwinbox's documentation says a user who connects and sees only the placeholder tool darwinbox_no_tools_or_agents_available has nothing assigned. An admin grants tools under Settings, AI Settings, MCP Registry by creating an MCP Configuration for your user assignment or permission role. Agents are enabled separately in the Agent Registry.
Why does a Darwinbox write tool say the connection was not granted permission?
Because your token carries read access only. Darwinbox's documentation says the mcp:read scope lists and runs read tools, while write tools, agents and file uploads need mcp:write. Tools outside the granted scope are hidden, and calling one returns an error asking you to reconnect. Disconnect, reconnect and approve write access, and the write tools appear if your admin has assigned them.
Do I need a client ID to connect Darwinbox to Claude?
Yes, for a custom connector. Darwinbox's setup guide says to enter the OAuth Client ID, and a Client Secret if one was issued, that your Darwinbox administrator gives you, under the connector's advanced settings. Darwinbox registers these OAuth clients itself, so administrators contact their Darwinbox account team to get one. On Claude Team and Enterprise, an Owner adds the connector once.
How long does a Darwinbox MCP sign-in last?
Up to 30 days, renewed silently while you use it. Darwinbox's documentation gives the access token a 15-minute life and the refresh token 30 days, rotated on every use. Reusing an old refresh token revokes every token issued from it, which forces a fresh sign-in. The sign-in itself must finish within 15 minutes of starting, or you have to begin again.
What is the difference between the Darwinbox MCP server URLs?
They decide what is listed, not what you may do. Darwinbox's documentation describes three URLs on one server: /mcp serves Darwinbox tools only and is the default, /mcp/agents serves agents built in Darwinbox Agent Builder, and /mcp/all serves both. Every call is still checked against your Darwinbox permissions and your admin's MCP configuration, whichever URL you connect to.
Live OAuth check: anonymous initialize POST to https://mcp.darwinbox.com/mcp/all, RFC 9728 metadata at https://mcp.darwinbox.com/.well-known/oauth-protected-resource/mcp/all, and authorization-server metadata at https://auth.darwinbox.com/.well-known/oauth-authorization-server (2026-11-18). · retrieved 2026-11-18
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Darwinbox to work.
Connect Darwinbox once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.