Skip to main content
Glama
ashby-mcp

ashby-mcp

by dewierwan

Related Servers

Alternatives to ashby-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      16
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to Homerun, an applicant tracking system. Enables AI-assisted candidate review: browse vacancies, inspect applications, and leave review notes.
      -
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      22
      196 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables AI hosts like Claude Desktop, Cursor, and VS Code to run AI-powered candidate screening end to end over stdio, from local resume parsing and ranked results to outreach emails, credit management, and interview scheduling. It exposes 26 structured tools covering screening jobs, candidate comparison, bias audits, and calendar connections while returning JSON responses and errors that don't crash the host.
      MIT

    TDQS

    A4/5.0

    Scored across 24 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues