smeet666/mcp-lever

Lever is recruiting software that thousands of companies
use to run their hiring, and every customer gets a public job board that comes
with it. Each board carries that company's open positions with their title,
their location, the team and department they sit in, the commitment they ask for,
the full advert, and the salary range where the company chose to publish one.
Lever hosts one board per company, on either its global or its European instance,
and publishes no index across them.
This server connects a chat client to those boards. You name the companies you
are interested in, and it turns each name into the site name that addresses its
board, searches their openings, filters them by location, team, workplace type,
country, salary or how recently they were posted, reads one opening in full, and
lists the wordings each company filters by. It needs no API key and no account.
_Version française_
---
Install
**One-click install**
**Claude Code**
**Claude Desktop, Cursor, and any client using the standard config format**
Node 24 or later is required, and no environment variable has to be set.
With Docker
-i keeps stdin open, which is where the protocol travels, and -t is left out
because a TTY rewrites the stream. The container needs outbound HTTPS to
api.lever.co and api.eu.lever.co, and nothing else: no volume, no port, no
credential.
Bundle, without npm
Download mcp-lever-2.0.1.mcpb from
the latest release and
open it. A client that supports MCP bundles installs it on its own, with no npm
and no configuration file to edit. The bundle carries its dependencies, so
nothing is fetched at install time.
What you can ask
- "Which of Included Health, Netlify and Ramp are hiring on Lever?"
- "Find me remote engineering roles at those three companies."
- "Read me that opening in full."
- "What locations does Included Health list its jobs under?"
- "Anything posted in the last two weeks at Netlify?"
Every question starts from a company, since Lever offers no search across boards.
search_jobs resolves the names you give it, so no preparation is needed:
Tools
| Tool | What it does |
| -------------------- | -------------------------------------------------------------- |
| resolve_company | Turns company names into the Lever site names of their boards. |
| search_jobs | Searches the openings of the companies you name. |
| get_job | Reads one opening in full, advert included. |
| list_filter_values | Lists the wordings one company files its openings under. |
A Lever site name distinguishes case, so Flex answers where flex returns
nothing. Four spellings are tried per name on each of the two instances, and the
answer lists what was sent, so nothing found is never proof that a company is
absent from Lever.
resolve_company
Turns company names into Lever site names, reporting every instance that
answered. It takes a list.
| Argument | Type | Required | What it does |
| -------- | ------------------------ | -------- | ---------------------------------------------------- |
| names | array of 1 to 25 strings | yes | Company names, or Lever site names you already know. |
**In return:** one entry per name, carrying input; found, a list of
{ slug, instance, publishes } where publishes is false for a site that exists
and lists nothing today; tried, the spellings sent in order; and cached, true
when this session had already resolved that name. A name answering on both
instances comes back with both, and neither is elected: pass the one you mean to
the other tools.
search_jobs
Searches the openings of the companies named. Lever applies the filters it
supports on its own exact wording, and this server applies the rest to the
openings it read.
| Argument | Type | Required | What it does |
| -------------------- | --------------------------------- | -------- | ----------------------------------------------------------------- |
| companies | array of 1 to 25 strings | yes | Company names or Lever site names. Each is resolved here. |
| keyword | string | no | Words to look for in the title and the advert. |
| location | array of 1 to 20 strings | no | Locations, exactly as Lever writes them. |
| team | array of 1 to 20 strings | no | Teams, exactly as Lever writes them. |
| department | array of 1 to 20 strings | no | Departments, exactly as Lever writes them. |
| commitment | array of 1 to 20 strings | no | Commitments, exactly as Lever writes them. |
| workplace_type | array of 1 to 4 strings | no | remote, hybrid, onsite or unspecified. |