Recruitee MCP connector
The Recruitee connector brings interview results, candidate notes, job opening notes, office locations, and admin lists into Claude, ChatGPT, Cursor, Microsoft Copilot, and other AI clients, so recruiters can ask about hiring activity in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Summarize this week's interview results by location.
Working in Recruitee with Elaichi
-
List all Recruitee interview results
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Recruitee to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Recruitee MCP connector for 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.
Recruitee MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Recruitee MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Recruitee MCP connector for 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.
Recruitee MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Recruitee through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Recruitee is logged.
-
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.”
What connecting Recruitee gets you
6 screens from Elaichi, each doing one job for your Recruitee account.
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, Cursor or Microsoft Copilot
The agent
Ask about interview results, read the answer.
Plain language questions answered from live Recruitee notes, interview results and locations.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Recruitee here.
One org-wide OAuth endpoint for Recruitee, no SDK and no shared API key.
ElaichiToolsTool catalog
5 Recruitee tools ready the moment you connect.
Browse tool names, resources and methods for Recruitee without writing custom code.
ElaichiToolboxesToolboxes
Every team gets its own Recruitee toolbox.
Recruiting, hiring managers and people ops each see the toolbox scoped to them.
ElaichiConnectionsShared connections
Teammates use Recruitee without seeing a credential.
Each Recruitee connection shows who connected it and which teams and members share it.
ElaichiAudit logAudit log
Every Recruitee call has a name on it.
When, who, what happened, type and resource for each Recruitee request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Recruitee digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Recruitee
Queued
Automations
A schedule fires, a hiring digest ships.
Recruitee interview results are fetched, grouped, drafted, approved by a person, then posted back.
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%
Collections and dashboards
Recruitee hiring numbers, computed not generated.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Recruitee
All three can connect Recruitee 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Recruitee tools | Allow or restrict single Recruitee 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 Recruitee 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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restrict specific things, such as the admin list, for a role. Anything restricted still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client together.
Does the Recruitee MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Recruitee 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, Microsoft Copilot, 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 Recruitee?
Yes. Both let Claude, ChatGPT or Cursor use Recruitee. 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 Recruitee call.
How is Elaichi different from Composio for Recruitee?
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 Recruitee: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Recruitee in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot