A Lever MCP server, so Claude can work with your Lever data

Status: no official server yet

Authentication

The API base is https://api.lever.co/v1.

For internal use, the API key is sent as the Basic-auth username. OAuth is available for registered partners.

Honest limits

• An API key gives the server access at the level of that key, not per recruiter. If each recruiter should act as themselves, that points to OAuth, which Lever offers to registered partners.
• Moving stages and archiving change live pipeline data. A read-only first build is an option.

How you’d connect it

The server runs two ways: locally over stdio, started with npx, or remotely over Streamable HTTP at a URL on your own host. The commands below use placeholders; your README has the real package name, URL and variables. NOLU does not run a shared hosted Lever server.

Claude Code

# remote (Streamable HTTP)
claude mcp add --transport http lever https://<your-host>/mcp

# local (stdio)
claude mcp add lever -e LEVER_API_KEY=<value> -- npx -y <your-server-package>

Claude Desktop

For a remote server, add the URL https://<your-host>/mcp as a custom connector. For a local server, add it to claude_desktop_config.json:

{
  "mcpServers": {
    "lever": {
      "command": "npx",
      "args": ["-y", "<your-server-package>"],
      "env": {
        "LEVER_API_KEY": "<value>"
      }
    }
  }
}

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "lever": { "url": "https://<your-host>/mcp" }
  }
}

Variable names above are examples. Keep credentials in local config or your host’s secret store, never in the repository.

Who it is for

• Lever customers (recruiting teams) who want Claude to work with their own Lever account, using their own credentials.
• Lever itself, if it wants an MCP server built around its API for its customers. That usually means the Standard tier, with OAuth so each user signs in with their own account.

Questions