# Recruitee MCP connector The Recruitee connector brings interview results, candidate notes, job opening notes, office locations, and admin lists into Claude, ChatGPT, Cursor, and other AI clients, so recruiters can ask about hiring activity in plain language. Source: https://elaichi.ai/connectors/recruitee/ ## Facts | | | | --- | --- | | Application | Recruitee | | Category | ATS | | AI tools | 5 | | Authentication | Connects with an API key | | Needs 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 | Yes | ## What you can ask once Recruitee is connected - Summarize this week's interview results by location. - Which admins left notes on open offers? - List notes added to candidates in Berlin. ## Connect Recruitee in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Recruitee. 2. Optionally set Share with, then press Connect. 3. Paste a Recruitee API key. One person generates a token in Recruitee and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Recruitee tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Recruitee to 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. ## Connect Recruitee to 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. ## Connect Recruitee to 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 Recruitee 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 Recruitee 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 Recruitee through Elaichi ### Round up interview results before a debrief Recruiting. Pull every scorecard submitted for the week and get a short read on how candidates landed with each interviewer before the panel meets. ### Catch up on a candidate's notes Hiring managers. Ask what the team has written about a candidate so far and walk into the next interview already knowing what colleagues flagged. ### See what the team said about an opening Talent acquisition. Read through the notes recruiters left on a job opening to understand why the brief changed or where the search is stuck. ### Check which offices are hiring People operations. List the locations set up in Recruitee to confirm a new opening is tied to the right office before it goes live. ### Review who has admin access in Recruitee HR. Get the current list of Recruitee admins and spot accounts that belong to people who have changed roles or left. ### Spot interviews missing a scorecard Operations. Compare interview results against the interviews that took place and nudge the people who still owe feedback. ## Frequently asked questions ### How do I connect Recruitee to Claude? Two steps. In Elaichi, choose Recruitee, paste in an API key generated from your Recruitee account settings, and save; there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude will ask you to sign in to Elaichi once, and Recruitee is ready to use. ### Does Recruitee work with ChatGPT and Cursor as well as Claude? Yes. Once Recruitee is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Recruitee once and use it everywhere your team already works. ### What can an AI agent actually do with my Recruitee data? With Recruitee connected, an agent can read interview results and summarize how candidates scored, pull up the notes colleagues left on a candidate, and show the notes attached to a job opening. It can also list your office locations and the people who hold admin access in Recruitee. This connector reads from Recruitee; it does not create, edit, or delete anything. ### Does connecting Recruitee give the AI access to every candidate and opening? No. Access follows the person who signed in, so an agent only sees the Recruitee interview results, notes, and openings that person could already see in Recruitee. Elaichi can narrow that further, for example limiting a team to interview results only, but it can never widen what Recruitee itself allows. ### Can my team share one Recruitee connection? Yes. One recruiter connects Recruitee in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every question asked of Recruitee is recorded under the name of the person who asked it. ### Can I stop an agent from deleting or changing things in Recruitee? The Recruitee connector is read-only, so an agent cannot change, delete, or create candidates, notes, or openings through it. Beyond that, restrictions in Elaichi work per action, so you can also hide specific things, such as the admin list, from a team. Anything blocked is never shown to the AI client at all, so no prompt can reach it. ### What happens to a Recruitee connection when someone leaves? When a person is offboarded in Elaichi, their access to Recruitee through every AI client ends at once. A Recruitee connection they shared keeps working for everyone else on the team. If you want to remove Recruitee entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together. ## All 5 Recruitee tools Every tool below is callable through https://api.elaichi.ai/mcp once Recruitee is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Recruitee interview results** (List). List interview results in Recruitee. Requires company_id. Returns id, candidate_id, admin_id, kind, and evaluation details for each interview result. - **List all Recruitee notes** (List). Get notes for a specific candidate in Recruitee. Requires company_id and id. Returns an array of notes containing fields such as admin_id, body, created_at, attachments, and visibility. - **List all Recruitee locations** (List). List locations in Recruitee for company_id. Returns locations with fields such as id (unique location ID), name, country_code, state_name/state_code, city, full_address, created_at, updated_at, archived_at, lang_code, and optionally translations plus active_offers_count, active_requisitions_count, and is_deletable. - **List all Recruitee offer notes** (List). List notes for an offer in Recruitee. Requires company_id and offer_id. Returns each note with id, text, admin_id, created_at, updated_at, and nested replies including visibility and reactions data. - **List all Recruitee admins** (List). List admins in Recruitee. Requires company_id. Returns admin details including id, name, email, and role.