Full read-write Claude connector for Lever
Make Claude advance candidates and add notes in Lever
Stop clicking through Lever to keep your pipeline current. Claude looks up candidates, moves them to the next stage, leaves interview notes and tags, and handles archiving only once you approve, all where your recruiting already happens.
Lever is an applicant tracking system and recruiting CRM where talent teams run their pipeline, from sourcing candidates to scheduling interviews and moving offers forward. People want Claude to do more than read the pipeline: to leave notes, advance stages, and act on candidates directly.
What is a Lever MCP server?
A Lever MCP server is a small hosted service that exposes Lever's data and actions to Claude over the Model Context Protocol, so Claude can people, time, and pay inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Lever's current connector do today?
Today, a default Claude connection to Lever is read-leaning at best: Claude can look up candidates, postings, and pipeline stages, but advancing a candidate, adding notes, or updating a posting is limited or unavailable. A custom Lever connector adds those write actions through its API, with scoped, human-in-the-loop controls.
What does full read-write Lever access unlock?
Full read-write Lever access lets Claude move a candidate to the next pipeline stage, add interview notes and feedback to a profile, apply or remove tags, archive candidates with a reason, and create or update job postings, all after you approve. The pipeline upkeep that used to mean clicking through Lever happens where the work already lives.
- Advance a candidate to the next stage in a posting's pipeline
- Add a note or interview feedback to a candidate profile
- Apply or remove tags to organize candidates
- Archive a candidate with a documented reason
- Create or update a job posting and its details
- Add a candidate to a posting after you confirm
Can Claude move a candidate to the next stage in Lever?
Moving a candidate to the next stage is exactly what a full read-write Lever connector handles. Claude advances the candidate through a posting's pipeline using Lever's write API, instead of the read-leaning default connection where stage changes are limited or unavailable. The action runs after you approve it.
Can Claude add interview notes and tags to a candidate in Lever?
Adding interview notes and tags is supported through a custom Lever connector. Claude can attach feedback to a candidate profile and apply or remove tags to keep candidates organized, writing directly to Lever rather than leaving you to retype notes after the fact, with each write kept reviewable.
Will Claude archive a candidate in Lever without my approval?
Archiving a candidate is a separate, gated action that requires a documented reason and runs only after you confirm it. Claude can stage the change and explain why, but you decide which actions go automatically. The connector also inherits your own Lever permissions, never more access than your role already has.
How a Lever connector works
We build a small MCP server that authenticates to Lever with OAuth or a scoped API key and the narrowest permissions the work needs. Read tools (look up candidates, postings, stages) and write tools (advance stage, note, tag, archive) are kept separate, and destructive or outbound actions like archiving require your confirmation. Claude only ever has the access your own Lever account already has, and we can add IP allowlisting where your setup supports it.
Frequently asked questions
Can Claude move a candidate to the next stage in Lever?
Will Claude archive or reject a candidate without my approval?
Does the Lever connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.