How to Connect Ashby to Claude (and What It Won't Do)
Ashby publishes an official MCP server — in open beta on every plan — so Claude can read your recruiting data directly: candidates, applications, jobs, interviews, offers, notes, and feedback. Connect it through OAuth, and Claude can answer “how many candidates are stalled in the onsite stage for the Staff Engineer role?” or “summarize the feedback on Priya Nair” without you exporting a thing. What it can’t do is notice a new application land and do something about it. The MCP server, like every Claude connector, only works when you’ve opened a chat and asked.
Below: what Ashby’s MCP server exposes, how to connect it, why “chat-only” hurts most in a high-volume pipeline, and how to make an applicant trigger real work.
What the official Ashby MCP server does
Ashby built and maintains its own MCP server, so there’s no third-party server to vet and no scraping. It uses the same permission model you already have in Ashby — you connect through OAuth, and Claude can only see and touch what your own login can. It’s read-oriented, exposing tools across your recruiting records:
- Search and retrieve. Pull context across candidates, applications, jobs, job postings, interviews, offers, notes, feedback, referrals, and hiring teams.
- Report on the pipeline. “Which reqs have gone two weeks without a new candidate?” or “list every offer extended this quarter and its status.”
- Synthesize a candidate. “Read the interview feedback on this finalist and give me the split between yes and no, with the reasons.”
In practice you type things like:
- “Show me candidates in final-round for the Design Lead role and who still owes feedback.”
- “Summarize the scorecards for the two people we’re deciding between.”
- “Which sourced candidates from last month never got a first reply?”
That last one is the tell. Claude can find the candidate who never got a reply. It can’t send the reply.
Connecting it takes a couple of minutes
Ashby’s MCP server is a remote connector you add in Claude:
- In Claude, open Customize → Connectors and search the list for Ashby.
- Select Ashby and click Connect.
- Sign in to Ashby if you aren’t already, then click Approve on the authorization screen.
- Ask Claude to list your open jobs to confirm the connection.
The connection is per-user OAuth, so it inherits the permissions your Ashby account already has. Reads are broad — candidates, applications, jobs, interviews, offers, notes, feedback. Writes exist but are deliberately narrow: create a candidate, add a note, move an application to another stage, and consider someone for a job. It’s still an open beta, so expect the tool set to keep changing.
Why “chat-only” is the wrong shape for a pipeline
Recruiting is a stream of events, not a place you go to ask questions. That’s exactly where a chat-only connector falls down.
A new application is a clock starting. The candidate experience data is brutal on time-to-first-response — a same-day reply converts far better than a three-day one. The MCP server won’t tell you a new application arrived; it waits for you to ask, by which point the clock has been running for hours.
Stage changes want to fire off logistics. A candidate moves to “Onsite” and now someone needs a scheduling email, a calendar hold, and a prep packet. Claude can see they moved when you ask later. It won’t act at the moment the stage flips.
It reads Ashby; it doesn’t reach your other tools. Even where the server can write, it acts inside Ashby. It can’t take the offer that just went out and drop a heads-up in Slack, email the candidate the logistics, or put the start date on the hiring manager’s calendar. Those are actions in other systems.
So Claude is a genuinely useful analyst for your pipeline — “help me make sense of where everyone is” — and structurally unable to be the coordinator who moves candidates along while you’re in back-to-back interviews.
Applications that trigger real work: Carly
Reading the pipeline is half the job; keeping it moving is the other half. A new applicant should get acknowledged. A candidate who reaches “Offer” should get logistics. Carly — an AI executive assistant that runs on triggers, in the cloud — handles that half:
- A new candidate applies in Ashby → Carly sends a same-day acknowledgment through Gmail or Outlook and, for roles you flag, proposes screen times against your calendar.
- A candidate moves to “Onsite” → Carly emails the scheduling details, books the calendar holds for the panel, and posts the agenda to the hiring team’s Slack channel.
- A candidate is marked rejected → Carly sends a warm, on-brand decline so nobody sits in silence for a week.
- You describe it in plain English — “when someone reaches the offer stage, email me the details and put a reminder on my calendar to follow up in two days” — and Carly interviews you, then builds the workflow with you.
To connect Ashby, paste your API key on carlyassistant.com/integrations. AI agents start at $35/month, and workflow steps that don’t use AI — sending the email, creating the calendar hold, posting to Slack — run free. Ashby is one of 200+ tools Carly connects to; see the full integrations list.
Side by side
| Claude + Ashby MCP | Carly | |
|---|---|---|
| Search candidates / jobs / feedback | Yes | Yes |
| Summarize scorecards | Yes | Yes |
| Acts when a new candidate applies | No | Yes, on triggers |
| Acts when a candidate changes stage | No | Yes |
| Sends the reply / books the interview | No | Yes |
| Posts to Slack, updates your calendar | No | Yes |
| Runs overnight with your laptop shut | No | Yes (cloud) |
| Setup | OAuth MCP + paid Claude plan | Paste API key, plain-English interview |
Frequently Asked Questions
Does Claude integrate with Ashby?
Yes. Ashby publishes an official MCP server, in open beta on all plans except analytics-only orgs. Find it under Customize → Connectors in Claude, click Connect, authorize with OAuth, and Claude can search and report across your candidates, jobs, interviews, offers, and feedback.
Is there an official Ashby Claude connector in the directory?
Yes. Ashby’s connector is listed in Claude’s connectors directory — search for Ashby under Customize → Connectors and click Connect. Earlier in the beta this required pasting the server URL into a custom connector; that’s no longer necessary.
Can Claude reply to candidates or move them through stages automatically?
No. The MCP server is chat-driven and leans toward reading. It has no event triggers, so it won’t act when a candidate applies or changes stage. For same-day replies and stage-triggered scheduling, use a trigger-based agent like Carly.
What does automated Ashby follow-up cost with Carly?
AI agents start at $35/month, and the non-AI steps — sending the acknowledgment, booking the interview holds, posting to Slack — run free, so an apply-to-acknowledge-to-schedule pipeline stays affordable.
More: Claude + Lever · Claude connectors · Can Claude send emails · AI agents for recruiters · Best AI tools for recruiters · Best AI executive assistants
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
