[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Lever API and MCP server

> Yes. Lever has a REST Data API that reads and writes opportunities, notes, feedback, stages and archive reasons, but you need an API key on a LeverTRM plan or a registered partner app with OAuth, and Lever's developer docs list no MCP server (checked 22 Oct 2026).

Applicant tracking and recruiting software for hiring teams: job postings, candidate pipelines with stages, interviews and feedback forms, notes, email and offers in one place.

## What is the Lever API?

Cotlet's Lever API exposes 12 endpoints for your own Lever account: list opportunities, get opportunity, list notes, list feedback, list postings, list pipeline stages, list archive reasons, change stage, archive opportunity, add note, update tags and email candidate. The list_opportunities endpoint returns lists opportunities in your pipeline, optionally for one posting, stage, tag or candidate email. Each endpoint takes simple JSON inputs like opportunity_id, cursor or stage and works both as an operation of the lever_read or lever_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 12 (7 read, 5 write)
- **Updated:** 2026-10-22

Yes. Cotlet is a hosted MCP server and REST API for Lever with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Lever have an official API?

Yes. Lever has a REST Data API that reads and writes opportunities, notes, feedback, stages and archive reasons, but you need an API key on a LeverTRM plan or a registered partner app with OAuth, and Lever's developer docs list no MCP server (checked 22 Oct 2026).

| Task | Lever official | Cotlet |
|---|---|---|
| List and read opportunities | Partly: GET /opportunities, only with an API key on a plan that includes the API, or a partner OAuth app | Yes |
| Read interview feedback | Partly: GET /opportunities/:opportunity/feedback, same access limit | Yes |
| Move an opportunity to another stage | Partly: PUT /opportunities/:opportunity/stage, same access limit | Yes |
| Archive an opportunity with a reason | Partly: PUT /opportunities/:opportunity/archived takes a reason; it has no field to email the candidate | Yes |
| Add a note with @mentions | Partly: POST /opportunities/:opportunity/notes, same access limit | Yes |
| Add and remove tags | Partly: addTags and removeTags on an opportunity, same access limit | Yes |
| Email a candidate | No: No email endpoint in the API reference | Yes |
| Run any of this from an AI agent without code | No: No official MCP server in the developer docs | Yes |

Sources: [Lever Developer: API Overview](https://hire.lever.co/developer/documentation), [Lever Help: Enabling and using the Criteria Corp integration (API key)](https://help.lever.co/s/article/Enabling-and-using-the-Criteria-Corp-integration-API-key), [Lever Help: Archiving opportunities](https://help.lever.co/hc/en-us/articles/20087373712541-Archiving-opportunities)

## For AI agents

```text
Yes. Lever has a REST Data API that reads and writes opportunities, notes, feedback, stages and archive reasons, but you need an API key on a LeverTRM plan or a registered partner app with OAuth, and Lever's developer docs list no MCP server (checked 22 Oct 2026).
Cotlet provides a hosted MCP server and REST API for Lever: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=lever, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    lever_read, lever_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/lever, each operation at its own route, e.g. PATCH /api/v1/lever/opportunities/{opportunity_id}/stage
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_opportunities, get_opportunity, list_notes, list_feedback, list_postings, list_stages, list_archive_reasons, change_stage, archive_opportunity, add_note, update_tags, send_email
Confirm      change_stage, archive_opportunity, add_note, send_email (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/lever-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=lever, requests Lever in the Cotlet console and creates an API key there.
2. The user signs in to Lever once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Lever for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Lever server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Lever MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Lever in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Lever only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Lever login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Lever's terms; Cotlet is not affiliated with Lever.
```

## What can an AI agent do in Lever?

Cotlet is best for recruiters and small hiring teams who want their AI agent to move candidates, archive them with a reason, add notes and send emails in Lever without an API key or running or fixing a server.

- **[Archive rejected candidates with a reason and email](https://cotlet.dev/integrations/lever-api-mcp-server/archive-rejected-candidates.md)** (runs: weekly): "Archive the Phone screen opportunities of the Senior Designer posting that I name below as Underqualified, and send each one a short, polite rejection email." → `list_opportunities`, `list_archive_reasons`, `get_opportunity`, `archive_opportunity`
- **[Advance candidates after positive interview feedback](https://cotlet.dev/integrations/lever-api-mcp-server/advance-candidates-after-feedback.md)** (runs: daily): "For the Phone screen stage of the Senior Designer posting, read the submitted feedback. Move candidates whose every form rates Hire or better to On-site interview and list the rest." → `list_stages`, `list_opportunities`, `list_feedback`, `change_stage`
- **[Log call notes on candidate profiles](https://cotlet.dev/integrations/lever-api-mcp-server/log-notes-on-candidate-profiles.md)** (runs: daily): "Add this to the Lever profile of aisha.khan@example.com: "Call 22 Oct: wants hybrid, two weeks notice, salary band fits." Mention Sam Okafor and tag her strong-referral." → `list_opportunities`, `get_opportunity`, `add_note`, `update_tags`
- **Weekly pipeline summary by stage** (runs: weekly): "Every Monday, list my published Lever postings with the number of opportunities in each stage and flag every stage that is empty." → `list_postings`, `list_stages`, `list_opportunities`
- **Follow up with candidates who went quiet** (runs: weekly): "Find opportunities in the Reached Out stage of the Senior Designer posting, write each one a short follow-up and wait for my OK before sending." → `list_opportunities`, `get_opportunity`, `send_email`

## Can Lever automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Lever connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to archive rejected candidates with a reason and email, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/lever/opportunities. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/lever/opportunities with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Lever.

### list_opportunities

Lists opportunities in your pipeline, optionally for one posting, stage, tag or candidate email. Access: read. REST: `GET /api/v1/lever/opportunities`. MCP: `lever_read → list_opportunities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `posting_id` | string | no | Posting ID from list_postings. |
| `stage` | string | no | Stage name from list_stages. |
| `tag` | string | no | Tag as written in Lever; the match is case sensitive. |
| `email` | string | no | Candidate email address. |
| `archived` | boolean | no | true lists archived opportunities. Default: false. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the name, headline, stage, posting, tags and creation date of each opportunity, in the order Lever lists them, plus next_cursor while more remain. Filters combine. Confidential opportunities show only when your Lever role can see them.

Example response:

```json
{
  "opportunities": [
    {
      "opportunity_id": "9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12",
      "name": "Marco Silva",
      "headline": "Product designer at Acme",
      "stage": "Phone screen",
      "posting": "Senior Designer",
      "tags": [
        "portfolio-strong"
      ],
      "created_at": "2026-10-12T08:40:00Z"
    },
    {
      "opportunity_id": "5c3d8a17-e2b4-49f6-8d01-7a9b6c4e2f05",
      "name": "Aisha Khan",
      "headline": "UX lead at Brightly",
      "stage": "Recruiter screen",
      "posting": "Senior Designer",
      "tags": [
        "portfolio-strong"
      ],
      "created_at": "2026-10-15T13:05:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_opportunity

Returns one opportunity with its stage, tags, sources, followers and archive state. Access: read. REST: `GET /api/v1/lever/opportunities/{opportunity_id}`. MCP: `lever_read → get_opportunity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |

Returns the profile fields Lever shows on the opportunity: contact name, emails, headline, stage, posting, owner, tags, sources, followers and the link to the profile. For an archived opportunity it also returns the archive reason and date. Notes and feedback come from list_notes and list_feedback.

Example response:

```json
{
  "opportunity_id": "5c3d8a17-e2b4-49f6-8d01-7a9b6c4e2f05",
  "name": "Aisha Khan",
  "headline": "UX lead at Brightly",
  "emails": [
    "aisha.khan@example.com"
  ],
  "stage": "Recruiter screen",
  "posting": "Senior Designer",
  "owner": "Jordan Pike",
  "tags": [
    "portfolio-strong"
  ],
  "sources": [
    "Referral"
  ],
  "followers": [
    "Jordan Pike",
    "Sam Okafor"
  ],
  "archived": null,
  "url": "https://hire.lever.co/candidates/5c3d8a17-e2b4-49f6-8d01-7a9b6c4e2f05"
}
```

### list_notes

Lists the notes in a candidate's profile story. Access: read. REST: `GET /api/v1/lever/opportunities/{opportunity_id}/notes`. MCP: `lever_read → list_notes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the notes of all the candidate's opportunities, newest first, with the author, date and text. Secret notes appear only when your Lever role may see them. A next_cursor is returned while more notes remain.

Example response:

```json
{
  "notes": [
    {
      "note_id": "a8f1d0c3-6e2b-4b79-8c15-0d9e3f7a2b46",
      "author": "Sam Okafor",
      "created_at": "2026-10-16T09:22:00Z",
      "secret": false,
      "text": "Portfolio is strong on mobile flows."
    }
  ],
  "next_cursor": null
}
```

### list_feedback

Lists the feedback forms submitted for an opportunity. Access: read. REST: `GET /api/v1/lever/opportunities/{opportunity_id}/feedbacks`. MCP: `lever_read → list_feedback`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |

Returns each form with its title, interviewer, completion date, the overall rating as the form's own label and the comment fields. A form not yet submitted has completed_at set to null. Forms are returned in the order of the Feedback section of the profile.

Example response:

```json
{
  "feedback": [
    {
      "feedback_id": "c64fb192-d6d8-42dc-ac82-47cb87e9839c",
      "form": "Phone screen feedback",
      "interviewer": "Sam Okafor",
      "completed_at": "2026-10-19T15:30:00Z",
      "rating": "3 - Hire",
      "comments": "Clear portfolio walkthrough, good questions about the team."
    }
  ]
}
```

### list_postings

Lists the job postings of your Lever account. Access: read. REST: `GET /api/v1/lever/postings`. MCP: `lever_read → list_postings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | string | no | Posting state as Lever shows it, for example published, internal, closed or draft. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the id, title, team, location and state of each posting. Use posting_id with list_opportunities to see the candidates of one job.

Example response:

```json
{
  "postings": [
    {
      "posting_id": "7d2b4e91-3a6c-4f08-b1e5-9c0a8d3f6e27",
      "title": "Senior Designer",
      "team": "Design",
      "location": "Remote, Europe",
      "state": "published"
    },
    {
      "posting_id": "1f8c5a30-9e4d-47b2-a6d3-5b0e7c2a9f14",
      "title": "Recruiting Coordinator",
      "team": "People",
      "location": "Berlin",
      "state": "published"
    }
  ],
  "next_cursor": null
}
```

### list_stages

Lists the pipeline stages of your account. Access: read. REST: `GET /api/v1/lever/stages`. MCP: `lever_read → list_stages`.

No parameters.

Returns the stage names in pipeline order, as your account defines them. Pipelines are customized, so use these names with list_opportunities and change_stage.

Example response:

```json
{
  "stages": [
    "New lead",
    "Reached out",
    "Responded",
    "New applicant",
    "Recruiter screen",
    "Phone screen",
    "On-site interview",
    "Offer"
  ]
}
```

### list_archive_reasons

Lists the archive reasons you can pick when archiving an opportunity. Access: read. REST: `GET /api/v1/lever/archive-reasons`. MCP: `lever_read → list_archive_reasons`.

No parameters.

Returns the reason names your account defines under Settings > Pipeline and archive reasons. Use one of these names as the reason of archive_opportunity.

Example response:

```json
{
  "reasons": [
    "Underqualified",
    "Withdrew",
    "Timing",
    "Position closed",
    "Offer declined",
    "Hired"
  ]
}
```

### change_stage

Moves an opportunity to another pipeline stage. Access: write, asks the user first. REST: `PATCH /api/v1/lever/opportunities/{opportunity_id}/stage`. MCP: `lever_write → change_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `stage` | string | yes | Target stage name from list_stages. |

Changes the stage of the one opportunity you name; the same candidate's other active opportunities stay where they are. Lever advises against moving candidates backward because it skews pipeline data, so the call is for forward moves. A stage that does not exist fails with an error that lists your stages. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "opportunity_id": "9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12",
  "name": "Marco Silva",
  "previous_stage": "Phone screen",
  "stage": "On-site interview",
  "changed_at": "2026-10-22T09:12:00Z"
}
```

### archive_opportunity

Archives an opportunity with an archive reason and can email the candidate. Access: write, asks the user first. REST: `POST /api/v1/lever/opportunities/{opportunity_id}/archive`. MCP: `lever_write → archive_opportunity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `reason` | string | yes | Archive reason name from list_archive_reasons. |
| `send_email` | boolean | no | true sends an email to the candidate as part of archiving. Default: false. |
| `email_body` | string | no | Text of the email. Required when send_email is true. |

Archives only the opportunity you name, not the candidate's other active opportunities. With send_email the email goes out in the same step, as with Archive + Send Now in Lever, and it cannot be recalled. A reason that your account does not define fails with an error that lists the reasons. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "opportunity_id": "2d6f9b83-a41e-4c07-9e52-b8c3a0f17d64",
  "name": "Dana Whitfield",
  "previous_stage": "Phone screen",
  "archived": {
    "reason": "Underqualified",
    "archived_at": "2026-10-22T09:14:00Z"
  },
  "email_sent": true
}
```

### add_note

Adds a note to a candidate's profile. Access: write, asks the user first. REST: `POST /api/v1/lever/opportunities/{opportunity_id}/notes`. MCP: `lever_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `text` | string | yes | Note text. Write @name to mention a Lever user. |
| `secret` | boolean | no | true makes it a secret note. Default: false. |
| `notify_followers` | boolean | no | true alerts the followers of the opportunity. Default: false. |

Saves the note on the opportunity and returns the users it mentioned. Lever emails every mentioned user and they cannot switch that off. A secret note is visible only to users with Sensitive Information Privileges and to those mentioned. A name that is not a Lever user fails and nothing is saved. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": "e5b09a72-4c18-4d63-9f2a-6a1c8d3b7e90",
  "opportunity_id": "5c3d8a17-e2b4-49f6-8d01-7a9b6c4e2f05",
  "secret": false,
  "mentioned": [
    "Sam Okafor"
  ],
  "followers_notified": false,
  "created_at": "2026-10-22T09:20:00Z"
}
```

### update_tags

Adds and removes tags on an opportunity. Access: write. REST: `PATCH /api/v1/lever/opportunities/{opportunity_id}/tags`. MCP: `lever_write → update_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `add` | array of strings | no | Tags to add. |
| `remove` | array of strings | no | Tags to remove. |

Returns the full tag list after the change. Tags reach nobody and one more call undoes a change, so this tool does not wait for your OK.

Example response:

```json
{
  "opportunity_id": "5c3d8a17-e2b4-49f6-8d01-7a9b6c4e2f05",
  "tags": [
    "portfolio-strong",
    "strong-referral"
  ]
}
```

### send_email

Sends an email to a candidate from their opportunity. Access: write, asks the user first. REST: `POST /api/v1/lever/opportunities/{opportunity_id}/emails`. MCP: `lever_write → send_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Opportunity ID from list_opportunities. |
| `subject` | string | yes | Email subject. |
| `body` | string | yes | Email text. |

Sends one email to the candidate and returns the address and time. Lever moves an opportunity in New Lead to Reached Out when you email it, and the response shows the stage after the send. A sent email cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "opportunity_id": "3a7c1e58-d9b2-4f60-8e41-c5d0a2b6f937",
  "to": "tom.becker@example.com",
  "subject": "Quick follow-up on Senior Designer",
  "sent_at": "2026-10-22T09:30:00Z",
  "stage_after": "Reached out"
}
```

## How do I connect Lever to Claude Code, Codex or Cursor?

Connecting Lever takes three steps: sign up, sign in to Lever once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Lever to your agent.

1. **Create an account** Sign up and add Lever in the console. Your API key is there too.

2. **Sign in to Lever in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Lever there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Lever tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Archive the Phone screen opportunities of the Senior Designer posting that I name below as Underqualified, and send each one a short, polite rejection email.
```

### Call Lever from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/lever with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/lever/opportunities/9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12/stage \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stage":"On-site interview"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "opportunity_id": "9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12",
  "name": "Marco Silva",
  "previous_stage": "Phone screen",
  "stage": "On-site interview",
  "changed_at": "2026-10-22T09:12:00Z"
}
```

## Why use Cotlet for Lever?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Lever yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Lever changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Lever to Cotlet?

Yes. You sign in to Lever yourself, in your own Cloud Browser, and we never save your password. Your agents only get Lever once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Lever integration?**

No, Cotlet is independent of Lever. Lever's own API is too limited for this work. Cotlet works through your own Lever account, the way you use Lever in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Lever in your console: your agents lose access at once and you stay signed in. Signing out of Lever in the browser works too, and Reset browser deletes the whole profile.

## Is there a Lever MCP server on GitHub?

Yes. Community Lever MCP servers exist on GitHub, usually maintained by one person. They call the Lever API with an API key, so they need a plan that includes the API. You install one on your own computer, create the key and keep it running yourself; when the API or your plan changes, it stops working until you fix it. Cotlet hosts the same kind of server for you, signs in to Lever like you do, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create a Lever API key, add it to each MCP client | Sign up, sign in to Lever once, add one MCP server or API key |
| When Lever changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Lever access | An API key in a file on your computer, readable by any program you run | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access ends | Tools fail until you create a new key or fix the plan | Your Cloud Browser keeps you signed in; if Lever logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Lever changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Lever API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Lever API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Lever account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Lever yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Lever only after you enable it. When Lever signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Lever, sign out of Lever in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Lever's terms:** You use your own Lever account and stay responsible for following Lever's terms. Cotlet is independent and not affiliated with Lever. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Lever in the console and press Request access. Then you create your API key and connect Lever there.

**Do I need to be technical?**

No. You sign in to Lever once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Lever to Cotlet?**

Yes. You sign in to Lever yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Lever once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Lever sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Lever cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Lever's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Lever sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Lever login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Lever offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a LeverTRM plan or an API key to use Cotlet?**

No. Cotlet works in your own Lever account through a sign-in, so it needs neither an API key nor the plan tier that includes the API. What each tool can do follows your Lever role; Lever lists Super Admin, Admin, Team Member and Limited Team Member for adding notes. If your plan includes the API and you have a developer, Lever's own API is a fine fit for custom code (checked 22 Oct 2026).

**Can my agent send an offer or schedule an interview?**

No. Cotlet has no tool to create or send offers, to schedule or reschedule interviews, or to edit postings and requisitions. Lever's API reference lists offers only to list and download. Offers and scheduling stay in Lever.

**Can my agent post or send messages in Lever without asking me?**

No. Every call to change_stage, archive_opportunity, add_note or send_email waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_tags runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Lever API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/lever from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.