# Personio Recruiting MCP connector The Personio Recruiting connector brings candidates, applications, jobs, job categories and stage transitions into Elaichi, so once connected, Claude, ChatGPT, Cursor or the Elaichi Agent can answer hiring pipeline questions as the person who signed in. Source: https://elaichi.ai/connectors/personiorecruiting/ ## Facts | | | | --- | --- | | Application | Personio Recruiting | | Category | ATS | | AI tools | 9 | | Authentication | App credentials | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Personio Recruiting is connected - Which applications for the Account Executive job moved stage this week? - Brief me on candidate Lena Fischer before tomorrow's interview. - Summarize the open jobs in the Engineering category. ## Connect Personio Recruiting in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Personio Recruiting. 2. Optionally set Share with, then press Connect. 3. Paste your Personio Recruiting app credentials. Personio Recruiting authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Personio Recruiting tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Personio Recruiting MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Personio Recruiting MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Personio Recruiting MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Personio Recruiting to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Personio Recruiting tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Personio Recruiting through Elaichi ### Brief yourself before an interview Recruiting. Ask for a candidate by name and get their application, the job they applied for and every stage it has passed through, in one place before the call starts. ### See where your open role stands Hiring managers. Pull up the applications for a job you own and find out which stage each one is in without asking the recruiter for an update. ### Write the weekly pipeline summary People Ops. List all open jobs in Personio Recruiting and the applications against each, then have the agent turn it into the Monday hiring update. ### Find where applications stall Talent acquisition. Look at stage transitions across a job to see how long applications sit in screening or interview before they move on. ### Check open roles by job category Leadership. Ask how many jobs are open in Engineering, Sales or Operations and how many applications each category has drawn this quarter. ### Spot candidates applying to several jobs Recruiting coordinators. Search candidates and their applications to see who has applied to more than one role, so the team can coordinate a single conversation. ## Elaichi vs Zapier MCP vs Composio for Personio Recruiting All three can connect Personio Recruiting to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over Personio Recruiting tools | Allow or restrict single Personio Recruiting tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per Personio Recruiting call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect Personio Recruiting to Claude? Connect Personio Recruiting in Elaichi by entering the app credentials from your Personio Recruiting settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Personio Recruiting is ready to use. ### Does Personio Recruiting work with ChatGPT and Cursor as well as Claude? Yes. Once Personio Recruiting is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Personio Recruiting once and every client picks it up. ### What can an AI agent actually do with my Personio Recruiting data? An agent connected to Personio Recruiting can list and look up candidates, applications, jobs and job categories, and trace the stage transitions an application has gone through. That means it can brief you on a candidate, tell you where the applications for a role stand, or summarize open jobs by category. This connector reads from Personio Recruiting; it does not create, change or delete anything. Short, specific asks like "applications for the Account Executive job" work better than long sentences. ### Does connecting Personio Recruiting give the AI everything in my recruiting workspace? No. Every call to Personio Recruiting runs under the person who signed in, so the agent sees the candidates, applications and jobs that person is allowed to see and nothing more. Elaichi can narrow that further with roles and restrictions, but it can never widen what Personio Recruiting itself permits. ### Can my team share one Personio Recruiting connection? Yes. One person connects Personio Recruiting in Elaichi and shares it with a team, and nobody else ever handles the credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Personio Recruiting request. ### Can I stop an agent from deleting or changing things in Personio Recruiting? This Personio Recruiting connector only reads, so no agent can change or delete a candidate, application or job through it. Beyond that, Elaichi restrictions work per action, and a restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it. ### What happens to a Personio Recruiting connection when someone leaves? Offboarding a person in Elaichi ends their access to Personio Recruiting at once, across every client they used. A shared Personio Recruiting connection keeps working for everyone else on the team. If you disconnect Personio Recruiting in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step. ### Does the Personio Recruiting MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. Personio Recruiting is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for Personio Recruiting? Yes. Both let Claude, ChatGPT or Cursor use Personio Recruiting. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Personio Recruiting call. ### How is Elaichi different from Composio for Personio Recruiting? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Personio Recruiting: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 9 Personio Recruiting tools Every tool below is callable through https://api.elaichi.ai/mcp once Personio Recruiting is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Personio Recruiting candidates** (List). List Personio recruiting candidates, sorted by last updated date, newest first. Returns: id, company, applications, first_name, last_name, email, gender, birthday, phone, location, available_from, linkedin_profile, created_at, updated_at, _meta. Max 200 per page, default 100. The updated_at.gt and updated_at.lt filters are mutually exclusive. Custom attributes and tags are not returned. - **Get single Personio Recruiting candidate by ID** (Get). Get a single Personio recruiting candidate by id. Returns: id, company, applications, first_name, last_name, email, gender, birthday, phone, location, available_from, linkedin_profile, created_at, updated_at, _meta. Custom attributes and tags are not returned. Required: id. - **List all Personio Recruiting applications** (List). List Personio Recruiting applications, sorted by last updated date, newest first. Returns: id, company, candidate, job, current_stage, application_date, channel, is_anonymized, hiring_team, created_at, updated_at, _meta. Max 200 per page; updated_at.gt and updated_at.lt are mutually exclusive; custom attributes and tags are not returned. - **Get single Personio Recruiting application by ID** (Get). Get a single recruiting application in Personio by id. Returns: id, company, candidate, job, current_stage, application_date, channel, is_anonymized, hiring_team, created_at, updated_at, _meta. Custom attributes and tags are not returned. Required: id. - **List all Personio Recruiting jobs** (List). List recruiting jobs for the authorized company in Personio, sorted by last updated date, newest first. Returns each job's id, name, category, company, department, hiring_team, created_at, and updated_at. updated_at.gt and updated_at.lt are mutually exclusive filters; up to 200 jobs returned per page. - **Get single Personio Recruiting job by ID** (Get). Get a single recruiting job in Personio by id. Returns the job object including its id, name, company, department, category, hiring team, and created/updated timestamps. Required: id. - **Get single Personio Recruiting job category by ID** (Get). Get a single job category in Personio Recruiting by id. Returns the category's id, company, name, and its ordered list of recruiting pipeline stages, where each stage has a kind, type, and (for custom stages) a name and id. Required: id. - **List all Personio Recruiting job categories** (List). List all job categories in Personio Recruiting. Returns each category's id, company, name, and ordered list of recruiting pipeline stages, where each stage has a kind, type, and (for custom stages) a name and id. - **List all Personio Recruiting application stage transitions** (List). List all stage transitions for an application in Personio Recruiting, ordered latest-first. Returns each transition's stage (kind, type, name, id) and entered_at (date-time, timezone). Required: application_id.