Ashby MCP. Manage your entire hiring pipeline via conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Ashby MCP Server connects your AI agent directly to your Ashby recruiting platform. Use it to manage your hiring pipeline by listing, searching, and retrieving details on jobs, candidates, and applications.
Your agent can track job statuses, find specific candidates by email, and monitor the full application lifecycle without you opening a single tab.
What your AI agents can do
Get account check
Verifies the connection and authentication status for your Ashby account.
Get application info
Retrieves specific details for a single job application record.
Get candidate info
Gets full profile details for a specific candidate.
Retrieves job listings based on keywords or titles.
Searches the candidate database using an email address or name to pull up full profiles.
Retrieves all detailed metadata for a specific job ID.
Pulls all details for a single job application ID.
Lists all job applications, allowing filtering by job ID or current workflow stage.
Retrieves a full list of all candidates stored in Ashby.
Lists all scheduled interviews for immediate oversight.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Ashby MCP Server: 10 Tools for Recruiting Pipelines
Use these tools to manage jobs, candidates, and applications within your Ashby account via natural language prompts.
019d7552get account check
Verifies the connection and authentication status for your Ashby account.
019d7552get application info
Retrieves specific details for a single job application record.
019d7552get candidate info
Gets full profile details for a specific candidate.
019d7552get job info
Retrieves detailed metadata for a specific job listing.
019d7552list applications
Lists all job applications in your account, allowing filtering by job ID or workflow stage.
019d7552list candidates
Retrieves a full list of all candidates currently stored in Ashby.
019d7552list interviews
Lists all scheduled interviews in your recruiting calendar.
019d7552list jobs
Lists all job listings, supporting filtering by status (e.g., open, closed).
019d7552search candidates
Searches the candidate database using either an email address or a name.
019d7552search jobs
Searches for job openings using keywords from the job title.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Ashby, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Ashby MCP Server hooks your AI agent right into your Ashby recruiting platform. You can use it to manage your whole hiring pipeline—from tracking job openings to monitoring candidate applications—without ever touching a single tab. Your agent handles all the heavy lifting.
Search for Job Openings: Your agent pulls job listings using keywords or titles. To get the full picture on a specific role, it retrieves all the detailed metadata for that job ID. You can also list every job, filtering by status like open or closed.
Find Candidates: You can search the candidate database using an email address or a name; the agent pulls up the full profile, including all the details. Need to see everyone? It retrieves a full list of all candidates stored in Ashby. For immediate oversight, it also lists all scheduled interviews for you.
Track Applications: The agent lists all job applications, letting you filter them by a specific job ID or by their current workflow stage. If you need the deep dive on one application, it pulls all the specific details for that single job application record. You'll also get a list of all job applications in your account, which lets you filter by job ID or workflow stage.
System Check: Before you start, the agent verifies the connection and authentication status for your Ashby account.
How it works: Your agent handles everything. You just tell it what you need, and it executes the complex queries across jobs, candidates, and applications, keeping you focused on hiring, not on data entry.
How Ashby MCP Works
- 1 Tell your agent what you need, like 'List all open jobs with status X.'
- 2 The agent calls the relevant tool (e.g.,
list_jobs) and sends the parameters. - 3 The server returns the structured data (e.g., a list of job titles and IDs) directly to your AI client.
The bottom line is you talk to your agent, and it talks to your Ashby account for the data.
Who Is Ashby MCP For?
This is for the recruiter who's tired of juggling 15 tabs just to see where a candidate stands. It's for the hiring manager who needs to quickly review candidate profiles without leaving their planning session. It gives talent operations staff a unified view of all hiring trends and application statuses.
Audits the full candidate pipeline and tracks application statuses across multiple roles instantly.
Reviews candidate profiles and job details using AI-assisted summaries during planning sessions.
Monitors hiring trends and ensures all applications move through the required workflow stages efficiently.
What Changes When You Connect
- See a candidate's full profile, tags, and contact details instantly using
get_candidate_info. You don't have to navigate to their profile page to get basic data points. - Stop manually cross-referencing job IDs. Use
list_applicationsto filter all jobs by workflow stage—like 'Hired' or 'Lead'—to see exactly where every applicant stands. - Get immediate oversight of your calendar using
list_interviews. You can pull a list of all scheduled interviews without logging into your calendar tool. - Find open roles without guessing. Use
search_jobsto quickly search the job title, andlist_jobsto filter by status (open, closed, etc.). - Audit the entire candidate pool using
list_candidatesandsearch_candidatesto pull up profiles by name or email. It's a massive time saver compared to manual searches. - Review specific job requirements on the fly. Use
get_job_infoto pull detailed metadata for any job ID, giving context to the current hiring stage.
Real-World Use Cases
Need to check a candidate's latest status?
A recruiter needs to confirm if 'Jane Doe' is still in the process. Instead of searching her name, they run search_candidates to get her ID. Then, they use get_application_info with that ID to confirm her current stage and assigned job.
I need to see all jobs that are currently open.
The hiring manager needs a list of all active roles. They run list_jobs and filter by 'open' status. This gives them the titles and IDs, which they can then pass to get_job_info to review the full job description.
What was the status of the 'Senior Frontend Engineer' job?
The talent ops specialist wants a quick audit. They use list_applications and filter by the Job ID for 'Senior Frontend Engineer'. This shows the count of applicants and their current stage, letting them quickly identify bottlenecks.
Need to find an applicant from a few months ago?
The recruiter remembers an applicant's email but not their name. They run search_candidates using just the email. This pulls up the full profile details, letting them resume communication instantly.
The Tradeoffs
Assuming one single data dump
Trying to get a full candidate profile by only listing all candidates (list_candidates) and then manually finding the details for each one.
→
Don't use list_candidates for specific data. First, use search_candidates to find the candidate's ID, then use get_candidate_info with that ID. That gives you the full profile in one shot.
Missing job context
Running list_applications and only seeing the job ID and status. You have no idea what the job actually is.
→
Always cross-reference. After running list_applications, take the Job ID and run get_job_info to get the full details and context for that specific job.
Forgetting the workflow stage
Only checking get_application_info and seeing 'Pending.' You don't know if 'Pending' means the candidate is waiting for the job description or if the hiring manager hasn't looked at it yet.
→
Use list_applications and specifically filter by the workflow stage. This gives you a clearer picture of the application bottleneck.
When It Fits, When It Doesn't
Use this server if your core workflow revolves around the candidate lifecycle—tracking, searching, and managing status changes. You need to connect the dots between a person (candidate), a role (job), and a status (application).
Don't use this if your primary need is something else, like managing payroll or logging sales leads. For those, you'll need a different system. If you just need to list all job titles without status filtering, list_jobs is fine, but if you need to know who applied and where they are in the process, you need the combination of list_applications and get_application_info.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Ashby. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking job applications shouldn't require 12 different clicks.
Today, tracking one candidate means opening the ATS dashboard, finding their name, clicking the application record, checking the status field, then potentially opening a separate tab to see the job description they applied for. It's a lot of manual switching and copy-pasting.
With this MCP server, you tell your agent: 'What is the status of candidate John Doe for the Senior Frontend role?' Your agent runs `search_candidates` and `get_application_info`. You get the status and the job context in one answer. Period.
Ashby MCP Server: Know the Candidate and Job Details
You currently have to pull candidate data from one place and job details from another. You manually match up IDs and descriptions to understand the full picture of the opening.
The server lets you combine `get_candidate_info` and `get_job_info` into one workflow. You instantly know who the person is and exactly what the job requires, without ever leaving your AI client.
Common Questions About Ashby MCP
How do I use the `list_jobs` tool to find only open roles? +
You pass 'open' as the status filter to the list_jobs tool. This returns a list of job titles and IDs that are currently active in Ashby.
Does `get_candidate_info` show me everything about the candidate? +
Yes. get_candidate_info pulls the full profile, including tags, contact details, and all stored metadata for that specific candidate.
Can I use `list_applications` to check multiple jobs at once? +
Yes. list_applications lets you list all applications, and you can filter the results by job ID or by the current workflow stage, which is really useful for auditing.
What's the difference between `search_candidates` and `list_candidates`? +
Use list_candidates to get a full, raw list of everyone. Use search_candidates when you know an email or name and only want to find that specific person quickly.
How do I check the connection status using `get_account_check`? +
You run get_account_check to verify the connection to Ashby. The output confirms if the API key is valid and if the agent has access to the platform's core data.
If I search for a candidate using `search_candidates`, what fields can I expect? +
The results provide the candidate's core identity and relevant metadata. You'll get the candidate's name, email, and any associated tags found in the profile.
Can `get_job_info` pull in historical data for a job? +
It pulls the full, current job listing details. This includes the job title, description, and the date the role was posted, but not past application records.
How do I handle too many applications when using `list_applications`? +
The tool handles pagination automatically. If you need more results, just ask your agent to fetch the next batch of applications. It manages the data flow for you.
How do I find my Ashby API Key? +
Log in to Ashby, go to Admin > API Keys, and click Create API Key. Ensure you grant the necessary permissions (e.g., jobsRead, candidatesRead).
Why does this server use POST for all requests? +
The Ashby API is designed as an RPC-style API where even data retrieval (reading) endpoints require a POST request with a JSON body.
Can I search for candidates by email? +
Yes, use the search_candidates tool and provide the email parameter to find a specific candidate in your database.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Lightcast Labor Market
Equip your AI agent to access labor market data, track skill taxonomies, and monitor job titles via the Lightcast API.
iSpring Learn
Train employees with a corporate LMS that delivers SCORM courses, tracks certifications, and generates compliance reports.
freee
Manage Japanese accounting and business via freee — track deals and invoices, handle partners and expenses, and audit tax codes directly from any AI agent.
You might also like
Cedar AI
Process insurance documents with AI that extracts claims data, validates coverage, and accelerates underwriting decisions.
Assembled
Manage support workforce and scheduling with Assembled — track agent states, teams, and forecasts via AI.
IBAN.com
Validate and audit banking codes — identify IBAN and SWIFT via AI.