Ashby logo ashbyhq.com

Live

Ashby API and MCP server

Ashby's API has no call to send the offer letter. Sign in to Ashby once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Ashby.

Ashby has no API for this. So we run one for you.

Ashby's own API, a GitHub MCP server and Cotlet compared
What you need Ashby's APIGitHub MCP serverCotlet
Offer letters No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Ashby changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 16, 2026. Sources: Ashby Knowledge Base: Ashby MCP Server (Beta) · Ashby product update: Ashby MCP · Ashby API reference: Introduction · Ashby API reference: endpoint index (llms.txt)

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Ashby in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Ashby to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Ashby and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/ashby with its own method and path, such as POST /api/v1/ashby/applications/{application_id}/archive, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Ashby API and MCP server do?

12 tools on your own Ashby account. Agents call them as operations of the MCP tools ashby_read and ashby_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Ashby tools in Cotlet's MCP server and REST API
Tool What it does Access
list_jobs Jobs with title, status, department and hiring team, open jobs by default. read
search_candidates Candidates by name or email, with their applications and current stage. read
get_candidate One candidate profile: applications, stage, notes, recent emails and scheduled interviews. read
list_applications Applications of a job with candidate, stage, status and days in stage, newest update first. read
list_interviews Scheduled interviews with time, interviewers and candidate, for one candidate or a date range. read
list_archive_reasons The archive reasons your admin set up, to use in archive_application. read
list_email_templates The email templates your account can apply, with name and purpose. read
schedule_interview Schedule an interview for an application with interviewers, time, video link and invite settings. writeasks first
send_email Send an email to a candidate from a template or your own text, now or at a set time. writeasks first
archive_application Reject an application with an archive reason, an optional note and an optional rejection email. writeasks first
create_offer Create an offer for an application in the Offer stage from your offer form fields. writeasks first
send_offer_letter Generate the offer letter, email it to the candidate and optionally request an e-signature. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All Ashby use cases

Is it safe to connect Ashby?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Ashby API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Ashby is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
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.

Questions

Does Ashby have an 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).

How do I get access?

Sign up free, open Ashby under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Ashby yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Ashby sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: schedule_interview, send_email, archive_application, create_offer, send_offer_letter wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Ashby MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Ashby changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Ashby?

No. Cotlet is independent and not affiliated with Ashby.

Give your agent access to Ashby.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free