ashby-mcp
Related Servers
Alternatives to ashby-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA server implementation that enables LLMs to interact with Ashby's Applicant Tracking System, allowing management of candidates, jobs, applications, interviews, and analytics through the Model Context Protocol.16MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables LLMs to interact with Ashby's Applicant Tracking System for managing candidates, jobs, applications, and interviews. It supports data operations, batch processing, and access to pipeline analytics and reporting.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to Homerun, an applicant tracking system. Enables AI-assisted candidate review: browse vacancies, inspect applications, and leave review notes.-
- AlicenseAqualityCmaintenanceAn MCP server that automates job applications by discovering postings from ATS boards, applying eligibility gates, scoring candidates, and drafting answers, while requiring human approval before submission. It respects anti-bot controls and only submits with explicit consent.221MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to interact with workplace tools like GitHub, GitLab, Jira, Notion, and more via the Model Context Protocol.1MIT
- AlicenseAqualityCmaintenanceMCP server for Recruit CRM, enabling AI assistants to search candidates, view jobs, and manage recruiting workflows.5348 PyPIMIT
TDQS
Scored across 24 tools
Most tools have clear boundaries: jobs, candidates, applications, interviews, archive reasons, and API docs are separated by verb and object. Some overlap exists (get_application_details includes feedback, making get_feedback partly redundant; list_applications and list_candidates_for_job both return pipeline lists), but descriptions usually steer the agent to the right tool.
The set consistently uses ashby_ + snake_case + verb_noun naming (list_jobs, get_candidate, move_application_stage). Minor deviations like bulk_archive (missing its object) and the generic call_api/get_api_docs pair keep it from being a perfect 5.
24 tools is at the heavy end of the 16-25 range. The breadth is understandable for an ATS, but the count is inflated by near-duplicates (archive_application vs bulk_archive, get_feedback vs get_application_details) and two meta-tools, so the set could be tightened.
Core recruiting workflows are covered: listing jobs, sourcing candidates, reading resumes/notes/form responses, moving stages, archiving, and reviewing feedback. Missing pieces like candidate updates, offer management, and interview scheduling are left to ashby_call_api, which prevents hard dead ends though it pushes work onto the agent.