Connect your AI to Lever
Give Claude, ChatGPT, Mistral or any MCP client secure access to Lever — no official Lever MCP server required. Proxoria turns Lever's API into tools your AI can use, with per-user authentication and write actions gated by your approval.
What your AI can do with Lever
Once connected, these tools appear automatically in your AI assistant:
list_postingsread-onlyList job postings. Filter by state, team, department, location, work type or tag, or group the results by one of those. Ask for `expand: ['owner', 'hiringManager']` to get the people behind each posting rather than their ids — Lever has no filter by person, so that is how you find someone's postings.
get_postingread-onlyGet one job posting by id, with its content, team, location and owners.
list_posting_usersread-onlyList the users who have access to a posting — its owner, hiring manager and followers.
list_opportunitiesread-onlyList candidates (opportunities). Filter by posting, stage, tag, email, origin or date. `origin: 'referred'` is how you find candidates who came through employee referral. `expand: ['applications', 'stage', 'owner', 'contact']` saves a call per candidate.
get_opportunityread-onlyGet one candidate (opportunity) by id.
list_applicationsread-onlyList a candidate's applications — one per posting they applied to, with the answers they gave to that posting's questions.
get_applicationread-onlyGet one application of a candidate in full.
list_resumesread-onlyList a candidate's résumés. Each carries `parsedData`: past positions (company, title, summary, location, dates) and schools (institution, degree, field, dates), already extracted by Lever — so matching a candidate to a posting needs no file download.
get_resumeread-onlyGet one résumé of a candidate, with its parsed positions and schools.
list_feedbackread-onlyList the interview feedback forms filled in for a candidate, with every field and score. This is where an interview panel's actual judgement lives.
list_feedback_templatesread-onlyList the feedback form templates of the account, with each field and its id. Required before create_feedback: the field ids of the values you submit come from here.
create_feedbackwrite · needs approvalFile a completed interview feedback form on a candidate. Lever records it under the user named in `performAs` and shows no sign that it was not typed by them — so only use this for someone who has told you what to record, never to invent an assessment. Take `baseTemplateId` and every field id from list_feedback_templates.
list_interviewsread-onlyList the interviews scheduled for a candidate, with their panel and interviewers.
list_referralsread-onlyList the referral forms filled in for a candidate. The referrer appears as a form field (often 'Name of referrer'), not as a Lever user — so counting who refers most means grouping on a typed name, and two spellings of one person will not merge. Find the candidates worth asking about with list_opportunities and `origin: 'referred'`; Lever publishes no account-wide list of referrals.
list_opportunity_notesread-onlyList the notes left on a candidate — the running commentary recruiters and managers add outside the formal feedback forms.
add_notewrite · needs approvalAdd a note to a candidate. Notes are visible to everyone with access to the candidate and cannot be edited afterwards. Give `performAs` to record it under a specific user; without it Lever attributes the note to the account the API key belongs to.
list_stagesread-onlyList the pipeline stages of the account.
list_usersread-onlyList the Lever users of the account — recruiters, hiring managers, interviewers. Their ids are what performAs and the posting owners refer to.
list_archive_reasonsread-onlyList the reasons an application can be archived for — why candidates were turned down, and which of those reasons count as hired.
Example prompts
Just ask your AI in plain language — it picks the right Lever tool:
- “List job postings. Filter by state, team, department, location, work type or tag, or group the results by one of those. Ask for `expand: ['owner', 'hiringManager']` to get the people behind each posting rather than their ids — Lever has no filter by person, so that is how you find someone's postings — from Lever, in plain language.”
- “Get one job posting by id, with its content, team, location and owners — from Lever, in plain language.”
- “List the users who have access to a posting — its owner, hiring manager and followers — from Lever, in plain language.”
- “List candidates (opportunities). Filter by posting, stage, tag, email, origin or date. `origin: 'referred'` is how you find candidates who came through employee referral. `expand: ['applications', 'stage', 'owner', 'contact']` saves a call per candidate — from Lever, in plain language.”
How it works
- Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
- Connect Lever with your API key — each user connects their own account, credentials encrypted at rest.
- Your AI instantly gets the Lever tools. Write actions wait for your approval in the dashboard before anything changes.
Frequently asked questions
- Does Lever have an official MCP server?
- You don't need one. Proxoria exposes Lever to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Lever MCP server required.
- What can my AI do with Lever through Proxoria?
- It gets 19 tools: list_postings, get_posting, list_posting_users, list_opportunities, get_opportunity, list_applications, get_application, list_resumes, get_resume, list_feedback, list_feedback_templates, create_feedback, list_interviews, list_referrals, list_opportunity_notes, add_note, list_stages, list_users, list_archive_reasons. For example, list job postings. filter by state, team, department, location, work type or tag, or group the results by one of those. ask for `expand: ['owner', 'hiringmanager']` to get the people behind each posting rather than their ids — lever has no filter by person, so that is how you find someone's postings.
- Is the Lever connector read-only?
- No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Lever.
- How do I connect Lever to my AI?
- Create a Proxoria account, connect Lever with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Lever tools.
Ready to connect Lever to your AI?
Set it up in minutes — no code, secure by default.
Get started freeAbout Proxoria. Proxoria connects AI assistants — Claude, ChatGPT, Mistral and any Model Context Protocol (MCP) client — to the business apps you already use, turning each app's API into tools your AI can call, with per-user authentication and write actions gated by human approval.