Ashby MCP connector
The Ashby connector brings jobs, candidates, and applications into Claude, ChatGPT, Cursor, and the Elaichi Agent, so recruiters can review a pipeline, move applications between stages, and tag candidates, all inside their own Ashby access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Ashby to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Ashby once
-
Open Connections, choose Add connection, and pick Ashby.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Ashby API key. One person generates a token in Ashby and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Ashby MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Ashby MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Ashby MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Ashby to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Ashby through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
Move an application on after a screen
Finish a phone screen, then ask the agent to move that candidate's Ashby application to the next stage and catch the record up while the call is still fresh.
-
Hiring managers
See where every open role stands
Ask which Ashby jobs are open, how many applications sit in each stage, and who the candidates are, without waiting for a recruiter to build a report.
-
Talent sourcing
Tag candidates and build a project
Tag Ashby candidates by skill or location and add them to a sourcing project so the shortlist for a hard-to-fill role is ready before kickoff.
-
Recruiting coordinators
Correct a source or transfer an application
When a referral came in through the careers page, change the application's source, or transfer an application to a better-fitting Ashby job without recreating it.
-
People operations
Open a new job and manage its status
Create the Ashby job for a newly approved headcount, then set it to on hold or closed as plans change, all from the same chat.
-
Legal and compliance
Anonymize a candidate on request
When a candidate asks for their details to be removed, anonymize their Ashby record and have the action, and who took it, recorded in the audit log.
Try asking
- “Which Ashby jobs are open with no active candidates?”
- “Summarize candidates added to the Platform Engineer job this week.”
- “Tag every referred candidate in Ashby from last month.”
Compare
Elaichi vs Zapier MCP vs Composio for Ashby
All three can connect Ashby to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Ashby tools | Allow or restrict single Ashby tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Ashby call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Ashby tools for your AI agents
111 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ashby, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Ashby gets you
6 screens from the product, each doing one job for your Ashby account.
The agent
Ask about candidates, get live Ashby answers.
Plain language questions run against real Ashby jobs, candidates and postings.
- jobs
- job postings
- candidates
- users
Ask Elaichi to work across your apps.
Which Ashby jobs are open with no active candidates?
Summarize candidates added to the Platform Engineer job this week.
Tag every referred candidate in Ashby from last month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Ashby here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
111 Ashby tools ready, no custom code.
Jobs, job postings, candidates and users, with every method listed and callable.
- List all Ashby jobs
- Get single Ashby job by ID
- Create a Ashby job
- Update a Ashby job by ID
Toolboxes
Every team gets its own Ashby toolbox.
Recruiting, hiring managers and finance each see a toolbox scoped to their work.
- Recruiting
- Hiring managers
- Sourcing
- People operations
Shared connections
Share an Ashby connection, never the credential.
See who connected each Ashby account and which teams and members use it.
- Recruiting EMEA
- Recruiting Americas
- Engineering hiring
- Sales hiring
Audit log
Answer who changed which Ashby candidate.
Every call recorded with time, person, action, type and Ashby resource touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and the hiring digest ships.
Ashby candidates are fetched, grouped, drafted by an agent, approved, then posted back.
Ashby digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
Ashby
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Ashby
Queued
Collections and dashboards
Ashby hiring numbers arrive before you ask.
Four metrics, 14 days of candidates created and a team breakdown, computed on schedule.
Ashby health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
Jobs
1,284 ↓ 12%
Job postings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Jobs created
Last 14 days
By team
Share of activity
Recruiting EMEA 34%
Recruiting Americas 27%
Engineering hiring 21%
Sales hiring 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Ashby to Claude?
Connecting Ashby to Claude takes two steps. In Elaichi, choose Ashby and paste in an Ashby API key from your Ashby admin settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, go to Customize, then Connectors, then Add, and enter https://api.elaichi.ai/mcp. Sign in to Elaichi when prompted and Ashby jobs, candidates, and applications are available in Claude.
Does Ashby work with ChatGPT and Cursor as well as Claude?
Yes. Once Ashby is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Ashby once and every client you use picks it up.
What can an AI agent actually do with my Ashby data?
With Ashby connected, an agent can list your open jobs and job postings, look up a candidate or application, move an application to a new stage, change its source, or transfer it to another job. It can create and update jobs, set a job's status, tag candidates and add them to projects, anonymize a candidate, and fetch a resume or other file attached to a record. Because Ashby has a large set of actions, short concrete asks such as "move Priya's application to onsite" work better than long paragraphs.
Does connecting Ashby give the AI access to every candidate and job?
No. Every call runs inside the Ashby access of the person who signed in, so an agent sees only the jobs, candidates, and applications that person could already open in Ashby. Elaichi can narrow that further, for example by hiding anonymize or stage changes from a team, but it can never widen access beyond what Ashby itself allows.
Can I stop an agent from deleting or changing things in Ashby?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Ashby jobs and candidates while blocking stage changes, job updates, or anonymizing candidates. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to an Ashby connection when someone leaves?
When you offboard someone in Elaichi, their access to Ashby through every connected client ends at once. If they had shared an Ashby connection with a team, that connection keeps working for everyone else. If you want Ashby removed entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Ashby MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Ashby is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Ashby?
Yes. Both let Claude, ChatGPT or Cursor use Ashby. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Ashby call.
How is Elaichi different from Composio for Ashby?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Ashby: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Ashby in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.