Skip to main content
Glama
antonber

ashby-mcp

by antonber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ashby-mcp

No user-submitted related servers found.

    Related Servers

    • Ashby MCP

      JakeTeagle
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects your Ashby recruiting data to Claude, enabling natural language queries and management of candidates, applications, jobs, interviews, offers, and team information.
      19 npm
      MIT

    • ashby

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching candidates, jobs, and applications in the Ashby ATS, retrieving detailed profiles and postings, and supports natural-language queries through Pipeworx's ask_pipeworx.
      5 npm
      MIT

    • MCP Ashby Connector

      thnico
      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

    • MCP Ashby Connector

      MCP-Mirror
      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

    • mcp-greenhouse

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search candidates, view job postings, and manage applications in Greenhouse ATS via natural language queries.
      4 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources