ashby-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASHBY_API_KEY | Yes | Your Ashby API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_candidatesB | Search for candidates in Ashby by name or email |
| get_candidateB | Get detailed information about a candidate including their applications |
| get_applicationC | Get details about a specific job application |
| list_candidate_applicationsA | List all applications for a candidate |
| submit_feedbackB | Submit interview feedback/scorecard for an application |
| get_application_feedbackA | Get all feedback submitted for an application |
| list_jobsB | List all open jobs |
| get_interview_scheduleC | Get interview schedule for an application |
| add_candidate_noteB | Add a note to a candidate in Ashby |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: searching candidates, getting candidate/application details, listing applications, submitting/retrieving feedback, listing jobs, getting interview schedules, and adding notes. No two tools have overlapping purposes, making selection unambiguous.
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_candidates, get_candidate, list_jobs). Verbs like search, get, list, submit, and add are clearly differentiated and used predictably across the set.
Nine tools is well within the ideal 3-15 range for an ATS integration. The scope is tight and focused on recruiting workflows—searching, viewing, feedback, and scheduling—without unnecessary bloat or missing core actions.
The tool surface covers the main candidate and application lifecycle: search, retrieve, list, provide feedback, view interview schedule, and add notes. Minor gaps exist, such as no job detail retrieval or application status updates, but these are not critical for common recruiting tasks.