Lever MCP server

What the model can do

Recruiting from Lever: job postings by state, team and location, candidates (opportunities) by posting, stage, origin or recency with their stage, owner and tags, one candidate's full picture with interviews, notes and offer status, the pipeline stages and archive reasons, and users. Never reads salary ranges or offer terms. When granted it can add notes, move candidates between stages, archive (reject or hire) or unarchive them, add candidates, tag them, submit interview feedback, create, edit, publish or close postings, create requisitions and deactivate users.

Reads

• lever_postingsJob postings in Lever (published by default): title, state (published, internal, closed, draft, pending, rejected), team, department, location…
• lever_opportunitiesCandidates in Lever's pipeline (opportunities): by posting, stage, origin (applied, sourced, referred, university, agency, internal), source, tag…
• lever_opportunityOne Lever candidate's full picture: profile with stage, postings, owner, origin and sources, every interview (when, who, where, stage)…
• lever_stagesThe Lever pipeline stages in order (id and name; stage ids filter lever_opportunities) and the archive reasons with their type…
• lever_usersUsers of the Lever account: name, email, access role (super admin, admin, team member, limited team member, interviewer) and whether deactivated.

Acts, when you ask

These change something in Lever. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• lever_add_noteAdds a note to a candidate's profile in Lever, where everyone with access to the candidate reads it; the candidate never sees it.
• lever_move_stageMoves a candidate (opportunity) to another pipeline stage in Lever, recorded against the acting user.
• lever_archive_opportunityArchives a candidate's opportunity in Lever with an archive reason (a rejection, a withdrawal, or Hired), or unarchives it with unarchive: true.
• lever_create_opportunityAdds a candidate to Lever as a new opportunity, optionally on one posting and in a given stage (default New Lead), with emails, links…
• lever_add_tagsAdds tags to a candidate's opportunity in Lever (a tag that does not exist yet is created).
• lever_remove_tagsRemoves tags from a candidate's opportunity in Lever.
• lever_submit_feedbackSubmits an interview feedback form (scorecard) on a candidate, as the acting user…
• lever_create_postingCreates a job posting in Lever, as a draft by default.
• lever_update_postingEdits a Lever job posting or changes its state; only the fields passed change.
• lever_create_requisitionCreates a requisition (approved headcount to hire against) in Lever.
• lever_deactivate_userDeactivates a Lever user: they can no longer log in, and their history stays.

Connect it

First connect Lever on Dashboard → Connections, then add Memtro to your client once. The Lever tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Lever connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who is in the Onsite stage for the Product Designer posting?
• › What interviews does Marcus Bell have scheduled, and who has left notes on him?
• › Which candidates were archived last month, and for what reasons?
• › Move Marcus Bell to the Offer stage
• › Add a note to Marcus Bell's profile: reference checks complete, both positive, ready for offer approval

Questions

Is this an official Lever MCP server?

No. It is Memtro's MCP server with Memtro's Lever connector behind it: the connector reads Lever through its API with the credentials you connect on Dashboard → Connections, and Lever publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Lever?

Only when you ask, and only what it has been granted: add a note to a candidate's profile; move a candidate to another pipeline stage; archive a candidate with a reason (reject, withdrawn or hired), or unarchive them; add a candidate as a new opportunity; add tags to a candidate; remove tags from a candidate; submit interview feedback on a candidate; create a job posting (draft, internal or published); edit a job posting or change its state (publish, close); create a requisition; deactivate a Lever user. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server