ATS
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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
5 tools
How to connect
How to connect Recruitee to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Recruitee once
-
Open Connections, choose Add connection, and pick Recruitee.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Recruitee to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Recruitee to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Recruitee through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
Round up interview results before a debrief
Pull every scorecard submitted for the week and get a short read on how candidates landed with each interviewer before the panel meets.
-
Hiring managers
Catch up on a candidate's notes
Ask what the team has written about a candidate so far and walk into the next interview already knowing what colleagues flagged.
-
Talent acquisition
See what the team said about an opening
Read through the notes recruiters left on a job opening to understand why the brief changed or where the search is stuck.
-
People operations
Check which offices are hiring
List the locations set up in Recruitee to confirm a new opening is tied to the right office before it goes live.
-
HR
Review who has admin access in Recruitee
Get the current list of Recruitee admins and spot accounts that belong to people who have changed roles or left.
-
Operations
Spot interviews missing a scorecard
Compare interview results against the interviews that took place and nudge the people who still owe feedback.
Try asking
- “Summarize this week's interview results by location.”
- “Which admins left notes on open offers?”
- “List notes added to candidates in Berlin.”
AI tools
Recruitee tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Recruitee, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Recruitee gets you
6 screens from the product, each doing one job for your Recruitee account.
The agent
Ask about interview results, read the answer.
Plain language questions answered from live Recruitee notes, interview results and locations.
- interview results
- notes
- offer notes
- locations
Ask Elaichi to work across your apps.
Summarize this week's interview results by location.
Which admins left notes on open offers?
List notes added to candidates in Berlin.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Recruitee here.
One org-wide OAuth endpoint for Recruitee, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
5 Recruitee tools ready the moment you connect.
Browse tool names, resources and methods for Recruitee without writing custom code.
- List all Recruitee interview results
- List all Recruitee notes
- List all Recruitee locations
- List all Recruitee offer notes
ElaichiToolsToolboxes
Every team gets its own Recruitee toolbox.
Recruiting, hiring managers and people ops each see the toolbox scoped to them.
- Recruiting
- Hiring managers
- People ops
- Talent sourcing
ElaichiToolboxesShared connections
Teammates use Recruitee without seeing a credential.
Each Recruitee connection shows who connected it and which teams and members share it.
- Recruiting EMEA
- Recruiting Americas
- Engineering hiring
- Sales hiring
ElaichiConnectionsAudit log
Every Recruitee call has a name on it.
When, who, what happened, type and resource for each Recruitee request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a hiring digest ships.
Recruitee interview results are fetched, grouped, drafted, approved by a person, then posted back.
Recruitee digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch interview results
Recruitee
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Recruitee
Queued
Collections and dashboards
Recruitee hiring numbers, computed not generated.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Recruitee health
Refreshed 4 minutes ago · every 15 minutes · from the interview results collection
Interview results
1,284 ↓ 12%
Notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Interview results created
Last 14 days
By team
Share of activity
Recruiting EMEA 34%
Recruiting Americas 27%
Engineering hiring 21%
Sales hiring 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Recruitee in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.