Ashby MCP Server
Ashby ATS operations including candidate, job, and application management.
Data last scanned today · Reviewed today
Overview
This MCP server provides a bridge between Ashby ATS and AI assistants, enabling natural language control over recruitment operations. It exposes 44 distinct tools across seven categories, allowing for complex tasks like candidate searching, interview scheduling, and custom field management directly within your workflow. The tool is designed for rapid deployment using the uv package manager, requiring only an Ashby API key to function. By offloading complex data aggregation to an AI, recruiters can perform advanced tasks like filtering archived candidates for re-engagement or generating detailed, context-rich hiring funnel reports.
Our verdict
With a security score of 30/100, this server is considered high-risk. The primary concern is that the implementation lacks a read-only mode, meaning every installation is granted full write access to your Ashby ATS environment. Because it is community-maintained rather than official and currently relies on a single contributor, potential users should exercise caution when handling sensitive recruitment data.
- Comprehensive toolset covering 44 distinct ATS operations
- Zero direct dependencies minimize potential supply-chain vulnerabilities
- Simplified installation process via uv package manager
- Detailed README documentation provided
- Full write access permissions for all connected sessions
- High bus-factor risk with only one contributor
- Community-maintained project lacking official vendor support
Tools
| Tool | Description | Risk |
|---|---|---|
| create_candidate | Create a candidate in Ashby. | medium |
| search_candidates | Search for candidates. | low |
| list_candidates | List candidates. | low |
| get_candidate | Get details for a specific candidate. | low |
| update_candidate | Update candidate information. | medium |
| create_job | Create a new job posting. | medium |
| search_jobs | Search for jobs. | low |
| list_jobs | List jobs. | low |
| get_job | Get details for a specific job. | low |
| update_job | Update job information. | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the minimum permissions required for the Ashby API key?
At a minimum, the key requires read and write access for candidates, as well as read access for jobs, projects, and hiring-process metadata. If you intend to use interview scheduling tools, you must also have the 'read interviews' scope enabled by an Ashby admin.
›Does the server require local installation of Python or git?
No, the server setup utilizes uvx, which automatically handles cloning the repository, creating a virtual environment, and installing all necessary dependencies.
›How do I update the server to the latest version?
If you are using Claude Code, simply restart your session. The uvx tool will automatically re-fetch the server on the next run if any updates are available.
›Can I use this server with Claude Cowork in the browser?
Yes, but because Cowork runs in a browser and cannot spawn local processes, you must deploy the server as an HTTP/SSE service. A render.yaml blueprint is provided to facilitate deployment to the Render platform.
›What should I do if I encounter a 403 Forbidden error?
A 403 error typically indicates that your shared team API key lacks the necessary permissions for the specific tool you are trying to use. Have an Ashby administrator grant the required scopes to your team key.
Badge
Maintain this server? Add the live badge to your README.