HR & Recruiting · Ashby + Claude
Ashby MCP with Claude: Automate Job Postings, Candidates and Hiring Insights
The short answer
Claude works with Ashby through the Model Context Protocol (MCP), a secure standard that lets Claude read information from Ashby and take approved actions in it. Claude can help post jobs, update candidate stages, track interview schedules and summarise hiring pipeline data, using access and sign-in controls your organisation sets.
What is Ashby?
Ashby is an applicant tracking system used by recruiting teams and hiring managers. It stores job postings, candidate profiles, interview plans and hiring data in one place. Talent acquisition leaders, recruiters and people operations teams use it to run hiring from first application to offer. It helps teams keep candidates moving and see how the hiring process is performing.
How Claude connects to Ashby through MCP
The Model Context Protocol (MCP) is an open standard that works like a universal adapter between Claude and other software. It lets Claude use a tool such as Ashby securely, reading information and taking actions with permissions the organisation controls. Instead of copying data by hand between systems, Claude can work directly with the records it is allowed to see.
Once connected, Claude can typically read job openings, candidate records, pipeline stages and interview schedules. It can also perform defined actions, such as drafting a new job posting, moving a candidate to the next stage or summarising which roles are slowing down. The exact actions depend on how the connection is configured for your team.
Permissions and approvals keep people in charge. Access is limited to what each workflow needs, following least-privilege principles. Consequential steps, such as sending an offer-stage update or changing a candidate's status, can require a named person to approve before anything happens. Every action can be logged, so your team can review what Claude did and when.
What you can automate
Drafting and publishing job postings
Hiring managers describe a role in a few sentences. Claude turns that brief into a clear, consistent job posting that matches your house style and required fields. A recruiter reviews the draft, and once approved, the posting can be created in Ashby. This saves time on repetitive writing and reduces the back-and-forth that often delays a new role going live.
Keeping candidate records up to date
Recruiters often spend hours moving candidates between stages and adding notes after calls. Claude can read a call summary or email thread and suggest the correct pipeline stage and a short note for the candidate record. The recruiter confirms the update. Records stay current, and the hiring team sees an accurate picture of where each person stands.
Coordinating interview schedules
Scheduling interviews across panels, time zones and candidate availability is slow work. Claude can review which interviews are planned, flag gaps where a panel is missing feedback, and draft reminders for interviewers. Coordinators keep control of the calendar and approve any invitations before they are sent, reducing missed interviews and last-minute changes.
Surfacing hiring pipeline insights
Leaders want to know which roles are stalled and where candidates drop out. Claude can analyse pipeline data in Ashby and explain the results in plain language, for example noting that a particular interview stage takes much longer than others. This gives people operations and department heads a quick, clear view without building reports by hand.
Preparing weekly hiring updates
Hiring managers often ask for a status summary each week. Claude can compile open roles, candidate counts by stage and upcoming interviews into a short update. A recruiter checks the summary for accuracy before it is shared, so leaders receive dependable information without the manual effort of gathering it.
An end-to-end workflow: New role to scheduled interviews
TriggerA hiring manager submits a request for a new engineering role in the company's approval system.
Claude reads the request and drafts a job posting that follows the company's template.
A recruiter reviews and approves the posting, which is then created in Ashby.
As applications arrive, Claude suggests the initial pipeline stage for each candidate based on screening notes.
When a candidate passes screening, Claude proposes interview slots that match the panel's calendar in Microsoft 365.
The coordinator approves the invitations, and Claude logs the scheduled interviews and reminders in Ashby.
OutcomeRoles go live faster, candidate records stay accurate, and interviews are scheduled with fewer delays. Typical results vary, but teams often report less time spent on administration and clearer visibility for hiring managers.
How we set it up
Free automation audit
We review how your recruiting team uses Ashby today and identify the workflows worth automating, such as posting, pipeline updates or scheduling. You leave with a clear list of priorities at no cost.
Secure connection with an API key
We connect Claude to Ashby using an API key, the sign-in method Ashby supports. The key is stored securely and scoped to the permissions each workflow needs, following least-privilege access.
Workflow design and approvals
We design the end-to-end workflow across Ashby and your other systems, such as Microsoft 365 or your HR records. We define which actions run automatically and which require a named person to approve.
Testing and launch
We test the workflow against real past roles and candidates to check accuracy. After testing, we launch with monitoring and audit logs turned on, so you can see every action Claude takes.
Team training and handover
We train recruiters, coordinators and hiring managers on how to work with Claude, review its suggestions and handle exceptions. We then hand over documentation and check in after launch.
Who benefits
- Talent acquisition leader
- Gains a clearer view of pipeline health and where hiring slows down, supported by plain-language insights.
- Recruiter
- Spends less time on repetitive updates, postings and scheduling, and more time with candidates.
- Hiring manager
- Receives faster job postings and timely, accurate status updates on open roles.
- People operations or IT lead
- Keeps control of access, approvals and audit logs while the team works more efficiently.
Security and control
- Least-privilege API access, limited to the data and actions each workflow requires.
- Named human approval for consequential actions such as stage changes that affect candidates.
- Audit logs of every action Claude takes in Ashby, available for review.
- Clear rules on candidate personal data, including what Claude may read and summarise.
- Regular review of workflows after launch to confirm they still match your hiring policy.
For teams in the US, UK, India and the Middle East
Organisations in the United States, the United Kingdom, India and the Middle East each have their own rules on handling candidate personal data. In India, the Digital Personal Data Protection Act, 2023 applies, while the UAE and Saudi Arabia have their own data protection laws. We design each workflow to respect the rules that apply to your organisation. Hosting regions for custom applications, including India, the United States, the United Kingdom and the European Union, are chosen to meet your data residency requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Ashby MCP server do?
The Ashby MCP server gives Claude a secure way to work with Ashby data. It allows Claude to read job, candidate and pipeline information and carry out defined actions within the permissions you set. It acts as the connection point, so Claude can assist with recruiting tasks without someone copying information between systems by hand.
Is connecting Claude to Ashby secure?
Security depends on how the connection is set up. We use an API key scoped to only the permissions each workflow needs, store it securely, and turn on audit logs. Consequential actions can require human approval. We also check the design against your data protection obligations before launch.
What can Claude do with Ashby once connected?
Typically, Claude can read job postings, candidate records, pipeline stages and interview schedules. It can draft job descriptions, suggest stage updates, flag scheduling gaps and summarise hiring metrics. The exact actions available depend on the workflow we design together with your team.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused project covering one or two workflows often takes a few weeks, including testing and training. We confirm the timeline after the free automation audit, once we understand your current process.
Which Ashby plan or permissions do I need?
Generally, you need an Ashby account with an API key that your administrator can create and scope. Access levels depend on your organisation's setup and the workflows you want. During the audit we check what your current account supports and recommend the permissions needed.