100+ integrations are ready to connect to your AI.Connect your first MCP

Lever MCP server for your AI

Ask where a candidate stands, see how many people sit in each stage and who has gone quiet, move people along, log notes and read feedback, all in the Lever account your hiring team already uses.

PopMCPLever

Where is Shane Smith in our hiring process, and what did his interviewers say?

Supported Lever tools

Every documented operation in Lever's Data API, with the everyday hiring tools loaded by default and the rest, from templates and requisition fields to user admin, webhooks, EEO answers and the audit log, one search away.

110 tools in the full catalog: 56 read and 54 write. 47 load by default, and the rest are found with tool search.

lever_add_contact_links

Add links, such as a LinkedIn profile, to the person behind an opportunity.

lever_add_opportunity_sources

Add sources to an opportunity.

lever_add_opportunity_tags

Add tags to an opportunity.

lever_create_opportunity

Add a candidate as a new opportunity, with JSON details only.

lever_get_opportunity

Read one opportunity by id, with its stage, owner, tags, sources, applications, urls and archive status.

lever_list_opportunities

List candidates' opportunities (one person's candidacy for a role), newest activity first.

lever_remove_opportunity_tags

Remove tags from an opportunity.

lever_update_opportunity_archived

Archive an opportunity with a reason id, change its reason, or restore it with reason null.

lever_update_opportunity_stage

Move an opportunity to a stage by stage id.

lever_apply_to_posting

Submit an application for a candidate to a published or unlisted posting, with their real details only.

lever_create_posting

Create a job posting.

lever_get_posting

Read one posting with its job description, categories, owner and links.

lever_get_posting_application_questions

Read a posting's application form: every question and whether it is required, with EEO questions when enabled.

lever_list_postings

List job postings in any state.

lever_update_posting

Change a posting: only the fields you send change.

lever_add_candidate

Add a person to Lever in one call, optionally on a posting and with a resume, which Lever reads to fill in missing details.

lever_archive_opportunity

Archive a candidate by the reason's name, such as Underqualified or Hired, or put them back with restore=true.

lever_candidate_overview

Everything about one candidate in one call: details, stage, owner, applications, notes, feedback, interviews, offers, files and resumes.

lever_download_document

Read a document on a candidate: an uploaded file, a resume or an offer.

lever_list_archive_reasons

List the reasons a candidate can be archived, each marked hired or non-hired, active or inactive.

lever_list_sources

List every source candidates came from, with how many opportunities have it.

lever_list_stages

List the pipeline stages with id and name.

lever_list_tags

List every tag on the account, with how many opportunities have it.

lever_move_to_stage

Move a candidate to a stage by the stage's name, such as Phone screen.

lever_outstanding_feedback

Who still owes interview feedback on an opportunity, following Lever's own rule: the interview happened, was not canceled, has a feedback template other than no-feedback, and the interviewer has no submitted form.

lever_pipeline_summary

How many active candidates sit in each stage, across the account or for one posting, and who has gone quiet.

lever_list_users

List the people on the Lever account with their id, name, username, email and access role.

lever_create_feedback

Submit a feedback form on an opportunity.

lever_create_note

Add a note to an opportunity, or a comment on an existing note with note_id.

lever_create_panel

Schedule interviews for an opportunity as a new panel.

lever_get_feedback_template

Read one feedback template with its fields.

lever_get_requisition

Read one requisition by its Lever id, from lever_list_requisitions.

lever_list_feedback

List the feedback forms submitted on an opportunity, with each interviewer's answers and score.

lever_list_feedback_templates

List the active feedback templates.

lever_list_interviews

List the interviews on an opportunity with date, duration, interviewers, location and feedback.

lever_list_notes

List the notes on an opportunity, with their comments, authors and times.

lever_list_panels

List the interview panels on an opportunity: each schedule of interviews with its times and stage.

lever_list_requisitions

List headcount requisitions with status, headcount, hired count, owner and custom fields.

lever_list_files

List the files on an opportunity, such as cover letters and portfolios.

lever_upload_opportunity_file

Attach a file to an opportunity.

lever_list_profile_forms

List the completed profile forms on an opportunity: extra information such as salary expectations or visa details.

lever_get_contact

Read one person's details: name, headline, location, emails and phones.

lever_list_referrals

List the referrals on an opportunity, with who referred the person and their answers.

lever_list_resumes

List an opportunity's resumes, with Lever's parsed work history and education.

lever_update_contact

Update a person's name, headline, location, emails or phones.

lever_list_offers

List an opportunity's offers with status, fields such as salary, and signature progress.

lever_upload_file

Store a file for 24 hours so lever_apply_to_posting can use it.

lever_list_deleted_opportunities

List opportunities deleted from Lever, for keeping another system in step.

lever_list_opportunity_file_actions

List file activity on an opportunity: uploads, resume imports and removals.

lever_remove_contact_links

Remove links from the person behind an opportunity.

lever_remove_opportunity_sources

Remove sources from an opportunity.

lever_add_requisition_field_options

Add options to a dropdown requisition field.

lever_create_requisition_field

Create a custom requisition field.

lever_delete_requisition_field

Delete a requisition field.

lever_delete_requisition_field_options

Remove options from a dropdown requisition field.

lever_get_requisition_field

Read one requisition field by its id, such as cost_center.

lever_list_deleted_postings

List postings deleted within a time window of at most 30 days.

lever_list_posting_users

See who can reach a posting: the users and roles with access, and whether access came through a role.

lever_list_requisition_fields

List the custom fields requisitions can carry, with their ids, types and options.

lever_update_requisition_field

Replace a requisition field.

lever_update_requisition_field_options

Rename options on a dropdown requisition field.

lever_get_archive_reason

Read one archive reason by id.

lever_get_stage

Read one pipeline stage by id.

lever_list_disposition_stages

The whole pipeline in one call: every stage with its milestone and order, and every archive reason.

lever_create_user

Add a person to the Lever account.

lever_deactivate_user

Stop a person from signing in to Lever.

lever_get_user

Read one user by id, from lever_list_users.

lever_reactivate_user

Let a deactivated person sign in to Lever again.

lever_update_user

Replace an user.

lever_create_feedback_template

Create a feedback template.

lever_create_form_template

Create a profile form template.

lever_create_interview

Add an interview to a panel made through the API (externallyManaged is true).

lever_create_requisition

Create a requisition.

lever_delete_feedback

Delete a feedback form from an opportunity.

lever_delete_feedback_template

Delete a feedback template made through the API.

lever_delete_form_template

Delete a profile form template made through the API.

lever_delete_interview

Delete an interview from a panel made through the API.

lever_delete_note

Delete a note made through the API.

lever_delete_panel

Delete a panel made through the API, with its interviews.

lever_delete_requisition

Delete a requisition.

lever_get_feedback

Read one feedback form by id, from lever_list_feedback.

lever_get_form_template

Read one profile form template with its fields, ready to fill in for lever_create_profile_form.

lever_get_interview

Read one interview by id, from lever_list_interviews.

lever_get_note

Read one note by id, from lever_list_notes.

lever_get_panel

Read one interview panel by id, from lever_list_panels.

lever_list_form_templates

List the active profile form templates.

lever_update_feedback

Change the saved answers on a feedback form.

lever_update_feedback_template

Replace a feedback template.

lever_update_form_template

Replace a profile form template.

lever_update_interview

Replace an interview on a panel made through the API.

lever_update_note

Replace a note made through the API: the whole note becomes what you send.

lever_update_panel

Replace a panel made through the API.

lever_update_requisition

Replace a requisition.

lever_create_webhook

Send Lever events to a web address.

lever_delete_file

Delete a file from an opportunity.

lever_delete_webhook

Delete a webhook made through the API.

lever_get_file

Read a file's details: name, type, size and upload time.

lever_list_webhooks

List webhooks with their event and address.

lever_update_webhooks

Change webhooks made through the API.

lever_create_profile_form

Add a completed profile form to an opportunity.

lever_get_profile_form

Read one completed profile form by id, from lever_list_profile_forms.

lever_get_public_posting

Read one published job from a company's public job site, with no key.

lever_get_referral

Read one referral by id, from lever_list_referrals.

lever_get_resume

Read one resume's parsed work history and education.

lever_list_eeo_responses

Equal employment answers without anything identifying the person, for totals.

lever_list_eeo_responses_pii

Equal employment answers tied to named people: gender, race, disability, veteran status.

lever_list_public_postings

Read a company's published jobs from its public job site, as a visitor sees them, with no key.

lever_get_diversity_survey

Read the diversity survey linked to a posting's location: its questions and answer choices, not anyone's answers.

lever_list_audit_events

List security activity, newest first: sign-ins, user and role changes, API keys and data exports.

lever_list_deleted_applications

List applications deleted within a time window of at most 30 days.

Connect Lever to Claude, ChatGPT and Claude Code

Credentials off one Lever screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

As a Lever Super Admin, open Settings, then Integrations and API, then API Credentials, and generate a key under the Data API. Tick the endpoints the AI may use, then paste the key into PopMCP. There is one field, and PopMCP finds your data center by itself.

API key••••••••••••3f7a
Act as this useryou@company.com
ConnectionVerified

Then just ask for the work

  • “Where is Shane Smith in our hiring process, and what did his interviewers say?”

    • candidate_overview
  • “How is the Infrastructure Engineer role going? Who has had no activity for two weeks?”

    • pipeline_summary
  • “Move Shane to the Phone screen stage and leave a note saying why”

    • move_to_stage
    • create_note
  • “Who still owes feedback on Shane's interviews?”

    • outstanding_feedback
  • “Add this person to the Product Designer posting, with the resume at this link”

    • list_postings
    • add_candidate
  • “Draft a posting for a Senior Recruiter in Berlin, and leave it unpublished”

    • create_posting
  • “Archive this candidate as Underqualified”

    • archive_opportunity

Use Lever from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Lever MCP server questions

What teams ask before putting Lever behind an AI client.

What does PopMCP need to connect Lever?

One Data API key. A Super Admin makes it under Settings, Integrations and API, API Credentials, and ticks which endpoints it may use. Lever shows the key only once. PopMCP stores it encrypted, works out whether your account is on Lever's global or EU data center, and shows you the account it belongs to. The key never reaches your AI client.

Which endpoints should I tick on the key?

Only what you want the AI to do. For reading, start with Opportunities, Contacts, Postings, Stages, Users, Notes, Feedback and Interviews. To let it make changes, add the matching write endpoints. If a tool needs one you did not tick, the AI is told which. Access to confidential roles is a separate choice that can only be made when the key is created.

Whose name do changes appear under in Lever?

Lever records most changes under a person. If your account has one Super Admin, PopMCP uses them and tells you when you connect. Otherwise add a teammate's email under More options, or the AI asks you who to use the first time it needs one. It can also name someone for a single change, by email or by name.

How is candidate data handled?

The endpoints you tick decide what Lever will hand over at all. An applicant's IP address and browser details are cut from every answer. A resume or offer is opened only when the AI is asked to read it. EEO answers and the audit log stay out of the everyday tool list, and the AI is told to read them only when asked.

Can the AI find someone by name?

Yes, with a limit. Lever's API has no search, so finding someone by email is exact, while a name is matched against the most recent active candidates. If several people fit, the AI gets them all back and asks which one you mean.

Can I stop the AI from changing anything?

Yes, in two ways. Every connection starts read-only, and an owner or admin can allow write actions later. Separately, tick only read endpoints on the key and Lever itself refuses every change.

Do I need a partner agreement or an approved app?

No. Lever's OAuth sign-in is only for approved partners, but any Super Admin can make a key today. Some features have their own conditions on Lever's side: the audit log is a paid add-on, and creating requisitions needs API management turned on in Lever's requisition settings.

Which Lever events can start a workflow?

PopMCP can watch for new candidates, stage moves, archives, deletions, changed postings, new requisitions, users, tags and sources by checking the matching lists for changes. Lever's webhooks also need a Super Admin to turn on each event group in its settings, so nothing is registered on your account for this.

Do I have to run or host the Lever MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect Lever to Claude Code?

Connect Lever in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Lever on the consent screen. The Lever tools are then available in that session, and no Lever credential is stored on your machine.

Why do only 47 of the 110 tools load by default?

Loading 110 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 47-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 110 here. A trigger is something PopMCP watches for you: 10 Lever events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Lever.

Connect Lever to your AI in minutes

Launch a hosted MCP endpoint for Lever, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP