Lever MCP connector
The Lever connector lets Claude, ChatGPT, Cursor and the Elaichi Agent read opportunities, postings, applications and offers in Lever and move candidates between stages, with each person signed in as themselves and every action logged.
-
How it connects. Connects over OAuth. 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 Lever to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lever once
-
Open Connections, choose Add connection, and pick Lever.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Lever app, then approve. Lever needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
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.
Lever 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.
Lever 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.
Lever 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 Lever 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 Lever through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
Catch the pipeline up after a debrief
After a debrief, ask for the candidates on a posting, move the ones who passed to the next stage, and see who is still waiting on feedback.
-
Hiring managers
See where your candidates stand
Ask which opportunities on your posting are in phone screen, onsite or offer without opening Lever or chasing the recruiter.
-
Recruiting ops
Draft and update job postings
Create a new posting from a hiring brief, then update the title, team or application questions when the role changes.
-
Sourcing
Pull resumes before an outreach session
List the resumes and applications attached to an opportunity so you know what a candidate has already sent in before you write to them.
-
People ops
Keep Lever seats in order
Add a new recruiter as a Lever user, deactivate someone who has left, and reactivate a hiring manager who is back from leave.
-
Leadership
Understand why candidates drop out
Ask for open offers this quarter and the archive reasons used most often on a posting to see where the funnel leaks.
Try asking
- “Which opportunities for the Senior Engineer posting are still in phone screen?”
- “Move Priya Shah to the onsite stage.”
- “List offers extended this week and who they went to.”
Compare
Elaichi vs Zapier MCP vs Composio for Lever
All three can connect Lever 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 Lever tools | Allow or restrict single Lever 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 Lever 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
Lever tools for your AI agents
54 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lever, 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 Lever gets you
6 screens from the product, each doing one job for your Lever account.
The agent
Ask about candidates, get answers from live Lever.
Type a question in plain language and the agent reads your Lever pipeline.
- opportunities
- postings
- applications
- offers
Ask Elaichi to work across your apps.
Which opportunities for the Senior Engineer posting are still in phone screen?
Move Priya Shah to the onsite stage.
List offers extended this week and who they went to.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Lever endpoint for Claude, ChatGPT and Cursor.
Connect Lever once and every MCP client signs in over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
54 Lever tools, ready without writing code.
Opportunities, postings, applications, offers, resumes and users, covered without custom code.
- List all Lever users
- Get single Lever user by ID
- Create a Lever user
- Update a Lever user by ID
Toolboxes
Each team gets its own Lever toolbox.
Recruiters, hiring managers and people ops each see only the toolbox scoped to them.
- Recruiting
- Hiring managers
- Recruiting ops
- People ops
Shared connections
Share a Lever connection, never the credential.
One recruiter connects Lever and teammates work through it without seeing a secret.
- Recruiting
- Hiring managers
- Engineering hiring
- Sales hiring
Audit log
Every Lever action, named, timed and kept.
The log shows who moved which candidate, when, and from which client.
- 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
Schedules start hiring digests, not prompts.
New Lever applications are fetched, grouped, drafted into a digest, approved, then posted back.
Lever digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch opportunities
Lever
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
Lever
Queued
Collections and dashboards
Lever pipeline numbers, refreshed without asking.
Opportunities created over 14 days, by team, computed on a schedule with no model involved.
Lever health
Refreshed 4 minutes ago · every 15 minutes · from the opportunities collection
Opportunities
1,284 ↓ 12%
Postings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Opportunities created
Last 14 days
By team
Share of activity
Recruiting 34%
Hiring managers 27%
Engineering hiring 21%
Sales hiring 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Lever to Claude?
Connect Lever in Elaichi first, then in Claude go to Customize, then Connectors, then Add and paste https://api.elaichi.ai/mcp. Lever needs an OAuth application registered inside your own Lever account, so one admin brings a client ID and secret once when connecting, and nobody else has to. After that, each person signs in to Lever as themselves when their client asks.
Does Lever work with ChatGPT and Cursor as well as Claude?
Yes. Lever is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Lever data?
It can list and look up opportunities, postings, applications, resumes, offers, stages and archive reasons in Lever, and move a candidate from one stage to the next. It can also create or update a posting, submit an application to a posting, and add, update, deactivate or reactivate Lever users. Short, concrete asks work better than long paragraphs, so 'move Priya to onsite' beats a full brief.
Does connecting Lever give the AI everything in my Lever account?
No. Every call runs as the person who signed in to Lever, so the agent sees the postings, candidates and offers that person can already see, and nothing beyond that. Elaichi can narrow that further per team or per action, but it can never widen what Lever itself allows.
Can I stop an agent from changing things in Lever?
Yes. Restrictions in Elaichi work per action, so you can allow reading opportunities and postings while blocking moving candidates, editing postings or deactivating Lever users. 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 Lever connection when someone leaves?
Offboarding that person in Elaichi ends their access to Lever through every AI client at once. A shared Lever connection keeps working for everyone else on the team. If you want the connector gone, disconnecting Lever once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Lever MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lever 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 Lever?
Yes. Both let Claude, ChatGPT or Cursor use Lever. 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 Lever call.
How is Elaichi different from Composio for Lever?
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 Lever: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lever 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.