Arxena exposes a remote Model Context Protocol (MCP) server so authorized AI clients can read and act on your recruitment workspace—org charts, candidates, jobs, and messaging—using the same data you see in the app.
X-API-KEY or Authorization: Bearer.Cursor supports url + headers directly. Open Settings → MCP → add a custom server:
{
"mcpServers": {
"arxena": {
"url": "https://mcp.arxena.com/mcp",
"headers": {
"X-API-KEY": "<your-workspace-api-key-jwt>"
}
}
}
}claude_desktop_config.json only launches stdio processes — it does not accept a url field. Use the mcp-remote bridge (same pattern as RapidAPI and other remote hubs). Add to mcpServers, then fully quit and reopen Claude Desktop (Cmd+Q):
{
"mcpServers": {
"arxena": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.arxena.com/mcp",
"--header",
"X-API-KEY: ${ARXENA_API_KEY}"
],
"env": {
"ARXENA_API_KEY": "<your-workspace-api-key-jwt>"
}
}
}
}Alternatively, use Settings → Connectors in Claude Desktop and add https://mcp.arxena.com/mcp for OAuth (see step 5).
Run the stdio server on your machine instead of the hosted endpoint. Clone the Arxena repo, build packages/twenty-mcp-server, then point Claude Desktop at dist/index.js:
{
"mcpServers": {
"arxena": {
"command": "node",
"args": ["/path/to/arxena/packages/twenty-mcp-server/dist/index.js"],
"env": {
"ARXENA_API_TOKEN": "<your-workspace-api-key-jwt>",
"ARXENA_BASE_URL": "https://app.arxena.com"
}
}
}
}Published directory integrations use OAuth 2.1 against https://mcp.arxena.com. Connect through the app store flow; at consent, paste your workspace API key JWT to authorize access to your data.
Claude callback URL: https://claude.ai/api/mcp/auth_callback
New to Arxena? Create a workspace first, then generate an API key from Developers settings.