[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)

# Ashby API and MCP server

> Yes. Ashby has a public API (API key, JSON calls) and, since 29 Jun 2026, an official MCP server in open beta, but the MCP changes only four things: it creates candidates, adds notes, moves an application to another stage and considers a candidate for a job (checked 16 Oct 2026).

Applicant tracking system for recruiting teams: jobs, candidate profiles, interview plans and stages, interview scheduling, emails, offers and e-signatures in one place.

## What is the Ashby API?

Cotlet's Ashby API exposes 12 endpoints for your own Ashby account: list jobs, search candidates, get candidate, list applications, list interviews, list archive reasons, list email templates, schedule interview, send email to candidate, archive (reject) application, create offer and send offer letter. The list_jobs endpoint returns jobs with title, status, department and hiring team, open jobs by default. Each endpoint takes simple JSON inputs like candidate_id, application_id or cursor and works both as an operation of the ashby_read or ashby_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-21

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

## Does Ashby have an official API?

Yes. Ashby has a public API (API key, JSON calls) and, since 29 Jun 2026, an official MCP server in open beta, but the MCP changes only four things: it creates candidates, adds notes, moves an application to another stage and considers a candidate for a job (checked 16 Oct 2026).

| Task | Ashby official | Cotlet |
|---|---|---|
| Search candidates and read their profiles | Yes: Official MCP reads candidates, notes, emails and feedback | Yes |
| List open jobs and applications by stage | Yes: Official MCP filters applications, jobs and openings | Yes |
| Schedule an interview | Partly: No scheduling tool in the official MCP; the public API lists interviewSchedule.create | Yes |
| Send an email to a candidate | Partly: No email tool in the official MCP; the public API lists candidate.addEmailMessage | Yes |
| Reject a candidate with an archive reason and email | Partly: No reject tool in the official MCP; the public API lists archiveReason.list and application.changeStage | Yes |
| Create an offer | Partly: No offer tool in the official MCP; the public API lists offer.create and offer.start | Yes |
| Send the offer letter | No: No offer letter endpoint in the API index | Yes |

Sources: [Ashby Knowledge Base: Ashby MCP Server (Beta)](https://docs.ashbyhq.com/ashby-mcp-server-beta), [Ashby product update: Ashby MCP](https://www.ashbyhq.com/product-updates/mcp), [Ashby API reference: Introduction](https://developers.ashbyhq.com/reference/introduction), [Ashby API reference: endpoint index (llms.txt)](https://developers.ashbyhq.com/llms.txt)

## For AI agents

```text
Yes. Ashby has a public API (API key, JSON calls) and, since 29 Jun 2026, an official MCP server in open beta, but the MCP changes only four things: it creates candidates, adds notes, moves an application to another stage and considers a candidate for a job (checked 16 Oct 2026).
Cotlet provides a hosted MCP server and REST API for Ashby: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=ashby, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    ashby_read, ashby_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/ashby, each operation at its own route, e.g. POST /api/v1/ashby/applications/{application_id}/archive
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_jobs, search_candidates, get_candidate, list_applications, list_interviews, list_archive_reasons, list_email_templates, schedule_interview, send_email, archive_application, create_offer, send_offer_letter
Confirm      schedule_interview, send_email, archive_application, create_offer, send_offer_letter (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/ashby-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=ashby, requests Ashby in the Cotlet console and creates an API key there.
2. The user signs in to Ashby once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Ashby 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 Ashby 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 Ashby 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 Ashby 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 Ashby 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 Ashby 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 Ashby's terms; Cotlet is not affiliated with Ashby.
```

## What can an AI agent do in Ashby?

Cotlet is best for recruiters and talent teams who want their AI agent to schedule interviews, send emails, reject candidates and create offers in Ashby, the steps its official MCP does not do, without running or fixing a server.

- **[Reject candidates and send rejection emails](https://cotlet.dev/integrations/ashby-api-mcp-server/reject-candidates-and-send-rejection-emails.md)** (runs: weekly): "List active applications in the Senior Backend Engineer job that sit in Application Review and were submitted more than 14 days ago. Reject the ones whose resume shows under 3 years of backend work with the archive reason "Not a fit", send the rejection email template "After screen" and show me the rest." → `list_applications`, `get_candidate`, `list_archive_reasons`, `archive_application`
- **[Schedule interviews for candidates in a stage](https://cotlet.dev/integrations/ashby-api-mcp-server/schedule-interviews-for-candidates.md)** (runs: daily): "For candidates who just moved to Technical Screen in the Senior Backend Engineer job, schedule the "Technical screen" interview with priya.nair@example.com for the first free slot on Thursday at 14:00, send the invite to the candidate and add a Google Meet link." → `list_applications`, `get_candidate`, `list_interviews`, `schedule_interview`
- **[Create an offer and send the offer letter](https://cotlet.dev/integrations/ashby-api-mcp-server/create-and-send-offers.md)** (runs: daily): "Ana Costa is in the Offer stage for Product Designer. Create her offer with base salary 95,000 and start date 16 Nov 2026, request approval, and when it is approved send the letter with the "Offer letter" email template." → `get_candidate`, `create_offer`, `send_offer_letter`
- **Email candidates waiting in a stage** (runs: weekly): "Find candidates who have been in the Hiring Manager Screen stage for more than 10 days, and send each the "Still interested" email template with a note that we are close to a decision." → `list_applications`, `list_email_templates`, `send_email`
- **Weekly pipeline digest by job** (runs: weekly): "Every Monday, list my open jobs and the number of active applications in each stage, and flag stages where candidates have waited more than 7 days." → `list_jobs`, `list_applications`

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

Yes. Cotlet does not replace your automation platform: it gives it a Ashby 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 reject candidates and send rejection emails, 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/ashby/jobs/{job_id}/applications. | 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/ashby/jobs/{job_id}/applications 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 Ashby.

### list_jobs

Jobs with title, status, department and hiring team, open jobs by default. Access: read. REST: `GET /api/v1/ashby/jobs`. MCP: `ashby_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Job status as Ashby shows it in the Jobs list, for example 'Open'. Default: Open. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the jobs of your Ashby organization that your account can see, open ones by default. Use the job_id from each item in list_applications. The status is the one Ashby shows in the Jobs list. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "4e8a1d73-2b60-4c95-9f1e-a7d3560b82c1",
      "title": "Senior Backend Engineer",
      "status": "Open",
      "department": "Engineering",
      "hiring_manager": "Priya Nair",
      "active_applications": 41
    },
    {
      "job_id": "b05c93e7-8a14-4f2d-b6c0-1e7d94a3f528",
      "title": "Product Designer",
      "status": "Open",
      "department": "Design",
      "hiring_manager": "Ana Costa",
      "active_applications": 18
    }
  ],
  "next_cursor": null
}
```

### search_candidates

Candidates by name or email, with their applications and current stage. Access: read. REST: `GET /api/v1/ashby/candidates/search`. MCP: `ashby_read → search_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name or email, or part of it. |
| `tag` | string | no | Only candidates with this tag from Add tags. |

Finds candidates whose name or email matches the query and returns each with the jobs they applied to and the stage of every application. Use candidate_id in get_candidate and send_email, and application_id in the write tools.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": "e1f7a309-4c52-4d8b-a063-9b25d7c1e840",
      "name": "Ana Costa",
      "email": "ana.costa@example.com",
      "applications": [
        {
          "application_id": "9c41b7a2-6e03-4d58-a1f9-3b8d25e07c64",
          "job": "Product Designer",
          "stage": "Offer",
          "status": "Active"
        }
      ]
    }
  ]
}
```

### get_candidate

One candidate profile: applications, stage, notes, recent emails and scheduled interviews. Access: read. REST: `GET /api/v1/ashby/candidates/{candidate_id}`. MCP: `ashby_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate ID from search_candidates. |

Returns the profile fields Ashby shows on the candidate page, plus every application with its stage and archive reason if archived. Notes and emails come newest first. Private fields appear only if your account can see them.

Example response:

```json
{
  "candidate_id": "e1f7a309-4c52-4d8b-a063-9b25d7c1e840",
  "name": "Ana Costa",
  "email": "ana.costa@example.com",
  "source": "Referral",
  "applications": [
    {
      "application_id": "9c41b7a2-6e03-4d58-a1f9-3b8d25e07c64",
      "job": "Product Designer",
      "stage": "Offer",
      "status": "Active",
      "offer": null
    }
  ],
  "notes": [
    {
      "author": "Priya Nair",
      "created_at": "2026-10-14T10:12:00+02:00",
      "text": "Strong portfolio, wants a start in mid November."
    }
  ],
  "recent_emails": [
    {
      "direction": "sent",
      "subject": "Next steps",
      "sent_at": "2026-10-12T09:30:00+02:00"
    }
  ],
  "interviews": [
    {
      "interview": "Design review",
      "start": "2026-10-13T15:00:00+02:00",
      "status": "Completed"
    }
  ]
}
```

### list_applications

Applications of a job with candidate, stage, status and days in stage, newest update first. Access: read. REST: `GET /api/v1/ashby/jobs/{job_id}/applications`. MCP: `ashby_read → list_applications`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `stage` | string | no | Stage name as in the job's interview plan, for example 'Application Review'. |
| `updated_before` | string | no | ISO date. Only applications not updated since then. |
| `archived` | boolean | no | true lists archived applications with their archive reason. Default: false. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists applications of one job, filtered by stage name and by how long ago they were last updated. Active applications by default; set archived to true to read archived ones with their reasons. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "applications": [
    {
      "application_id": "7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742",
      "candidate": "Chris Nowak",
      "candidate_id": "a6d30b95-7e12-4c48-8f05-2c91e4b7d3a0",
      "stage": "Application Review",
      "status": "Active",
      "days_in_stage": 19
    },
    {
      "application_id": "3f60c8d1-9a27-4e53-b184-d7a05e2c9b36",
      "candidate": "Mei Tanaka",
      "candidate_id": "c82e5f17-0b94-4a6d-93e8-5f1a7d0c4b29",
      "stage": "Application Review",
      "status": "Active",
      "days_in_stage": 16
    }
  ],
  "next_cursor": null
}
```

### list_interviews

Scheduled interviews with time, interviewers and candidate, for one candidate or a date range. Access: read. REST: `GET /api/v1/ashby/interviews`. MCP: `ashby_read → list_interviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | no | Only interviews of this candidate. |
| `from` | string | no | ISO date. Default: today. |
| `to` | string | no | ISO date. Default: 14 days after from. |

Returns the interviews already scheduled in Ashby, soonest first. Pass candidate_id to see one candidate, or a date range to see what is booked across the team, for example to check an interviewer for clashes before schedule_interview.

Example response:

```json
{
  "interviews": [
    {
      "interview": "Technical screen",
      "candidate": "Lena Fischer",
      "start": "2026-10-23T11:00:00+02:00",
      "duration_minutes": 45,
      "interviewers": [
        "priya.nair@example.com"
      ],
      "location": "Google Meet"
    }
  ]
}
```

### list_archive_reasons

The archive reasons your admin set up, to use in archive_application. Access: read. REST: `GET /api/v1/ashby/archive-reasons`. MCP: `ashby_read → list_archive_reasons`.

No parameters.

Returns the archive reasons an Ashby admin keeps under Admin > Jobs & Applications > Archive Reasons. archive_application accepts only these names. Ashby asks for a reason on every archive.

Example response:

```json
{
  "archive_reasons": [
    {
      "name": "Not a fit"
    },
    {
      "name": "Position filled"
    },
    {
      "name": "Candidate withdrew"
    }
  ]
}
```

### list_email_templates

The email templates your account can apply, with name and purpose. Access: read. REST: `GET /api/v1/ashby/email-templates`. MCP: `ashby_read → list_email_templates`.

No parameters.

Returns the templates shown in the template dropdown of the Ashby email editor that your account can use, such as rejection, scheduling and offer emails. Pass a name to send_email, archive_application or send_offer_letter.

Example response:

```json
{
  "templates": [
    {
      "name": "After screen"
    },
    {
      "name": "Still interested"
    },
    {
      "name": "Offer letter"
    }
  ]
}
```

### schedule_interview

Schedule an interview for an application with interviewers, time, video link and invite settings. Access: write, asks the user first. REST: `POST /api/v1/ashby/applications/{application_id}/interview/schedule`. MCP: `ashby_write → schedule_interview`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `application_id` | string | yes | Application ID from list_applications or get_candidate. |
| `interview` | string | yes | Interview type name from the job's interview plan, for example Technical screen. |
| `start` | string | yes | ISO 8601 start time with offset. |
| `duration_minutes` | integer | yes | Length of the interview. |
| `interviewers` | array | yes | Interviewer emails, one slot each. |
| `location_type` | string | no | 'google_meet', 'zoom', 'microsoft_teams' or 'custom'. Default: custom. |
| `location` | string | no | Location text, only with location_type 'custom'. |
| `notify_candidate` | boolean | no | Send the calendar invite to the candidate. Default: false. |
| `notify_interviewers` | boolean | no | Send the calendar invite to interviewers. Default: false. |
| `confirmation_email` | boolean | no | Send the Candidate Confirmation Email. Default: false. |

Creates an interview the way Manual Schedule does: interview type, start time, length and interviewers, with a Google Meet, Zoom or Microsoft Teams link or custom location text. The candidate and interviewers get calendar invites only if you set notify_candidate and notify_interviewers; the confirmation email is off unless you turn it on. Needs Elevated Access as Hiring Manager or Admin, or Organization Admin. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "interview_id": "f4a1c096-3d78-4e25-8b9c-0a6e57d2b813",
  "interview": "Technical screen",
  "start": "2026-10-22T14:00:00+02:00",
  "duration_minutes": 45,
  "interviewers": [
    "priya.nair@example.com"
  ],
  "location": "Google Meet",
  "candidate_invited": true,
  "confirmation_email_sent": false
}
```

### send_email

Send an email to a candidate from a template or your own text, now or at a set time. Access: write, asks the user first. REST: `POST /api/v1/ashby/candidates/{candidate_id}/emails`. MCP: `ashby_write → send_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate ID from search_candidates. |
| `template` | string | no | Template name from list_email_templates. Or set subject and body. |
| `subject` | string | no | Subject, when no template is used. |
| `body` | string | no | Email body, when no template is used. |
| `send` | string | no | 'immediately' or 'scheduled'. Default: immediately. With 'scheduled', set send_at. |
| `send_at` | string | no | ISO 8601 date and time with offset, only with send set to scheduled. |

Sends an email to the candidate from the Ashby profile, so it appears in the candidate's email history. Give either a template name or a subject and body; substitution tokens in a template are filled by Ashby. Scheduled emails can be viewed and rescheduled only by the person who drafted them, which is your connected account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "email_id": "a09d3e72-5b16-4c84-97f0-e2c48b1d6a35",
  "candidate_id": "e1f7a309-4c52-4d8b-a063-9b25d7c1e840",
  "subject": "Still interested?",
  "status": "sent",
  "sent_at": "2026-10-16T09:00:00+02:00"
}
```

### archive_application

Reject an application with an archive reason, an optional note and an optional rejection email. Access: write, asks the user first. REST: `POST /api/v1/ashby/applications/{application_id}/archive`. MCP: `ashby_write → archive_application`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `application_id` | string | yes | Application ID from list_applications or get_candidate. |
| `archive_reason` | string | yes | Reason name from list_archive_reasons. |
| `note` | string | no | Optional note stored with the archive reason. |
| `email_template` | string | no | Rejection email template from list_email_templates. Without it no email is sent. |
| `send` | string | no | 'immediately' or 'scheduled'. Default: immediately. With 'scheduled', set send_at. |
| `send_at` | string | no | ISO 8601 date and time with offset, only with send set to scheduled. |

Archives the application for that job only and moves the candidate to the Archived stage, like Archive in Ashby. The reason must be one from list_archive_reasons. A rejection email goes out only if you name a template, immediately or at the time you set. Other applications of the same candidate stay active. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "application_id": "7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742",
  "status": "Archived",
  "archive_reason": "Not a fit",
  "note_added": true,
  "rejection_email": {
    "template": "After screen",
    "status": "sent"
  }
}
```

### create_offer

Create an offer for an application in the Offer stage from your offer form fields. Access: write, asks the user first. REST: `POST /api/v1/ashby/applications/{application_id}/offers`. MCP: `ashby_write → create_offer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `application_id` | string | yes | Application ID from list_applications or get_candidate. |
| `fields` | object | yes | Offer form values keyed by field title, for example {"Base salary": "95000"}. |
| `opening_id` | string | no | Opening ID, required when your organization turned on Require Openings for Hires. |
| `request_approval` | boolean | no | Submit the approval request after creating. Default: false. |

Fills the Offer Details form with the values you give, keyed by field title as set under Admin > Offers > Offer Custom Fields, and submits it. The application must be in the Offer stage. With request_approval set it also submits the approval request, which notifies the approvers; with approvals on, no letter can go out until every step is done. Needs Organization Admin, or the permissions Can See Candidate Profiles, Can Add/Edit Candidates and Can See Private Fields. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "offer_id": "6b3e90d4-1f87-4a52-8c06-d94a7e215b03",
  "application_id": "9c41b7a2-6e03-4d58-a1f9-3b8d25e07c64",
  "fields": {
    "Base salary": "95000",
    "Start date": "2026-11-16"
  },
  "approval_requested": true,
  "approvers": [
    "Hiring Manager",
    "Finance"
  ]
}
```

### send_offer_letter

Generate the offer letter, email it to the candidate and optionally request an e-signature. Access: write, asks the user first. REST: `POST /api/v1/ashby/offers/{offer_id}/letter`. MCP: `ashby_write → send_offer_letter`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `offer_id` | string | yes | Offer ID from create_offer or get_candidate. |
| `email_template` | string | yes | Email template from list_email_templates. |
| `request_signature` | boolean | no | Also send the e-signature request. Default: false. |
| `signatory` | string | no | Company signatory email, when the template has company tokens. |

Runs Generate Offer Letter, drafts the email from the template and sends it, as View Offer does in Ashby. If your organization uses approvals, the call is refused until every approval step is complete. An e-signature request is added only if the letter template has candidate e-signature tokens and you set request_signature. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "offer_id": "6b3e90d4-1f87-4a52-8c06-d94a7e215b03",
  "letter_generated": true,
  "email_template": "Offer letter",
  "email_status": "sent",
  "signature_requested": true
}
```

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

Connecting Ashby takes three steps: sign up, sign in to Ashby 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 Ashby to your agent.

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

2. **Sign in to Ashby in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Ashby 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 Ashby 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.

```
List active applications in the Senior Backend Engineer job that sit in Application Review and were submitted more than 14 days ago. Reject the ones whose resume shows under 3 years of backend work with the archive reason "Not a fit", send the rejection email template "After screen" and show me the rest.
```

### Call Ashby 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/ashby 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 POST https://cotlet.dev/api/v1/ashby/applications/7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742/archive \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"archive_reason":"Not a fit","note":"About 1 year of backend work; the role asks for 3 or more.","email_template":"After screen","send":"immediately"}'
```

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

```
{
  "application_id": "7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742",
  "status": "Archived",
  "archive_reason": "Not a fit",
  "note_added": true,
  "rejection_email": {
    "template": "After screen",
    "status": "sent"
  }
}
```

## Why use Cotlet for Ashby?

**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 Ashby 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 Ashby changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Ashby to Cotlet?

Yes. You sign in to Ashby yourself, in your own Cloud Browser, and we never save your password. Your agents only get Ashby 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 Ashby integration?**

No, Cotlet is independent of Ashby. Ashby's own API is too limited for this work. Cotlet works through your own Ashby account, the way you use Ashby 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 Ashby in your console: your agents lose access at once and you stay signed in. Signing out of Ashby in the browser works too, and Reset browser deletes the whole profile.

## Is there a Ashby MCP server on GitHub?

Yes. Community Ashby MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it access to Ashby, and keep it running yourself; when Ashby changes, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, give it access to Ashby, add it to each MCP client | Sign up, sign in to Ashby once, add one MCP server or API key |
| When Ashby 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 Ashby access | Credentials in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you sign in again by hand | Your Cloud Browser keeps you signed in; if Ashby 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 Ashby 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 Ashby API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Ashby 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 Ashby 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 Ashby 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 Ashby only after you enable it. When Ashby 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 Ashby, sign out of Ashby 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.
- **Ashby's terms:** You use your own Ashby account and stay responsible for following Ashby's terms. Cotlet is independent and not affiliated with Ashby. [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 Ashby in the console and press Request access. Then you create your API key and connect Ashby there.

**Do I need to be technical?**

No. You sign in to Ashby 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 Ashby to Cotlet?**

Yes. You sign in to Ashby yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Ashby 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 Ashby 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 Ashby 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 Ashby's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Ashby 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 Ashby 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?**

Ashby 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).

**Why not just use the official Ashby MCP server?**

Use it for reads and for its four writes: create a candidate, add a note, change an application's stage and consider a candidate for a job. It has no tool for scheduling interviews, sending emails, rejecting candidates or creating offers, and it is an open beta that an Organization Admin must turn on under Admin > Organization Setup > Opt-In Features. Cotlet covers those missing writes and works next to it.

**What role does my Ashby account need?**

It depends on the tool. Manual interview scheduling needs Elevated Access as Hiring Manager or Admin, Admin (Private) or Organization Admin. Creating offers needs Organization Admin or the permissions Can See Candidate Profiles, Can Add/Edit Candidates and Can See Private Fields. Approvals need the Plus, Enterprise or Legacy Plus plan.

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

No. Every call to schedule_interview, send_email, archive_application, create_offer or send_offer_letter waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Ashby 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/ashby 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.