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 mcp add lever -- npx -y mcp-lever

Claude Desktop, Cursor, and any client using the standard config format

{
  "mcpServers": {
    "lever": {
      "command": "npx",
      "args": ["-y", "mcp-lever"]
    }
  }
}

Node 24 or later is required, and no environment variable has to be set.

With Docker

{
  "mcpServers": {
    "lever": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-lever:2.0.1"]
    }
  }
}

-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:

resolve_company(["Included Health"])  ->  includedhealth, global instance, publishing
search_jobs(["Included Health"], keyword: "therapist")
get_job("includedhealth", "6f97a19f-…")

Tools

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.

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.

Lever itself applies location, team, department and commitment; this server applies keyword, workplace_type, country, salary_min, salary_interval, currency and posted_within_days to what it read. list_filter_values publishes the wordings the first four take, and a wording Lever does not know comes back as an empty list.

In return: jobs, each carrying id and company_slug, which get_job takes, plus title, location, all_locations, country, workplace_type, team, posted_at, url and apply_url. commitment and department are absent when the company records neither. salary is null for an opening published without one, which is never the same as zero, and it carries the interval Lever wrote it in, never converted or annualised. per_company gives one outcome per company, with a status of read, unresolved, empty or failed, which are four different answers, and the read and returned counts around the filters. total_available is always null: Lever publishes no result count. The rows carry no advert text, since one company's board can run to megabytes.