SmartRecruiters MCP connector
The SmartRecruiters connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read jobs, candidates, interviews, offers, and screening answers from SmartRecruiters, and update candidate status, with every call running as the signed-in person and logged.
-
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.
How to connect
How to connect SmartRecruiters to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SmartRecruiters once
-
Open Connections, choose Add connection, and pick SmartRecruiters.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SmartRecruiters API key. One person generates a token in SmartRecruiters 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.
SmartRecruiters 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.
SmartRecruiters 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 today. The plugin directory lives at chatgpt.com/plugins.
SmartRecruiters 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.
Connect SmartRecruiters 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 SmartRecruiters through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
Review a candidate before the screening call
Ask for a candidate's application, screening answers, and attached resume in one go, so the recruiter joins the call already knowing what was submitted.
-
Recruiting
Move candidates forward after a debrief
After the hiring team agrees, ask the agent to update each candidate's status in SmartRecruiters and confirm who is now at which stage.
-
Hiring managers
See where every open job stands
List the jobs you own, who is on each hiring team, how many candidates sit at each stage, and which postings are live right now.
-
Coordinators
Check this week's interview schedule
Pull every interview booked across SmartRecruiters for the week, grouped by job, so no candidate is left waiting on a confirmation.
-
HR
Confirm candidate consent before sharing details
Check which candidates have given consent in SmartRecruiters and which have not, before a profile is forwarded to anyone outside the hiring team.
-
Leadership
Track job approvals and open positions
Ask which jobs are waiting on approval, which positions are still unfilled by department, and how each job's status has changed over time.
Try asking
- “Which candidates for the Account Executive job are still in screening?”
- “Summarize screening answers for candidates in the Sales Engineer pipeline”
- “List this week's interviews and who sits on each hiring team”
Compare
Elaichi vs Zapier MCP vs Composio for SmartRecruiters
All three can connect SmartRecruiters 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 SmartRecruiters tools | Allow or restrict single SmartRecruiters 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 SmartRecruiters 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
SmartRecruiters tools for your AI agents
49 tools are ready to call through Elaichi's MCP endpoint the moment you connect SmartRecruiters, 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 SmartRecruiters gets you
6 screens from the product, each doing one job for your SmartRecruiters account.
The agent
Ask about your pipeline in plain language.
Get answers about jobs, candidates, interviews, and offers straight from SmartRecruiters records.
- jobs
- candidates
- interviews
- offers
Ask Elaichi to work across your apps.
Which candidates for the Account Executive job are still in screening?
Summarize screening answers for candidates in the Sales Engineer pipeline
List this week's interviews and who sits on each hiring team
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every AI client, no shared key.
Use SmartRecruiters from Claude, ChatGPT, or Cursor through one governed org endpoint.
Copy the endpoint
Tool catalog
49 SmartRecruiters tools, ready without writing code.
Jobs, candidates, interviews, offers, consents, and publications, all covered without custom code.
- List all SmartRecruiters jobs
- Get single SmartRecruiters job by ID
- SmartRecruiters jobs approval
- SmartRecruiters jobs hiring team
Toolboxes
Each team gets its own SmartRecruiters toolbox.
Recruiters, hiring managers, and HR each work from a toolbox scoped to them.
- Recruiting
- Hiring managers
- HR
- Talent operations
Shared connections
Share one SmartRecruiters connection, never the key.
Teammates work through the connection while the API key stays with whoever connected it.
- Recruiting
- Hiring managers
- HR
- Talent ops
Audit log
Every SmartRecruiters action is logged with a name.
See who viewed a candidate or changed a status, when, and on which record.
- When
- Who
- What happened
- Type
Launching 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 starts real work, a person approves.
Fetch new candidates, group them by job, draft a digest, approve, update SmartRecruiters.
SmartRecruiters digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
SmartRecruiters
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
SmartRecruiters
Queued
Collections and dashboards
SmartRecruiters hiring numbers, computed without a model.
Four metrics, a 14 day candidates chart, and a team breakdown, refreshed on schedule.
SmartRecruiters health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
Jobs
1,284 ↓ 12%
Candidates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Jobs created
Last 14 days
By team
Share of activity
Recruiting 34%
Hiring managers 27%
HR 21%
Talent ops 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect SmartRecruiters to Claude?
Connect SmartRecruiters in Elaichi by pasting the API key from your SmartRecruiters admin settings, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once Claude has signed in to Elaichi, your SmartRecruiters jobs, candidates, and interviews are available in the conversation.
Does SmartRecruiters work with ChatGPT and Cursor as well as Claude?
Yes. The SmartRecruiters connection in Elaichi is exposed through one endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent all connect to that same address. You connect SmartRecruiters once and every client you use picks it up.
What can an AI agent actually do with my SmartRecruiters data?
An agent can list and look up jobs, candidates, interviews, job ads, postings, and departments in SmartRecruiters, read a candidate's application, screening answers, offers, consents, and attachments, and check a job's hiring team and approval history. It can also move a candidate to a new status. Short, specific asks such as "candidates in screening for the Account Executive job" work better than long paragraphs.
Does connecting SmartRecruiters give the AI access to every candidate and job?
The AI sees exactly what the SmartRecruiters account that was connected can see, and nothing beyond it. Elaichi can narrow that further, for example limiting a team to reading candidates without changing their status, but it never widens what SmartRecruiters itself allows.
Can I stop an agent from changing candidate statuses in SmartRecruiters?
Yes. In Elaichi, restrictions on the SmartRecruiters connection apply per action, so you can allow reading jobs and candidates while blocking status updates. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter how the prompt is worded.
What happens to a SmartRecruiters connection when someone leaves?
Offboarding the person in Elaichi ends their access to SmartRecruiters through every AI client at once. A SmartRecruiters connection shared with a team keeps working for everyone else on it. If you want it gone altogether, disconnecting SmartRecruiters once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the SmartRecruiters MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. SmartRecruiters 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 SmartRecruiters?
Yes. Both let Claude, ChatGPT or Cursor use SmartRecruiters. 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 SmartRecruiters call.
How is Elaichi different from Composio for SmartRecruiters?
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 SmartRecruiters: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put SmartRecruiters in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.