Skip to main content
Glama
Comradery64

open-greenhouse-mcp

by Comradery64

Related Servers

Alternatives to open-greenhouse-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Production-ready MCP server for Greenhouse ATS with 175 tools for recruiting teams — manage candidates, applications, jobs, interviews, and hiring pipelines. Role-based profiles (full/recruiter/read-only), composite workflow tools for pipeline views, analytics, candidate search, and bulk operations.
      100
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Greenhouse (beta): https://www.cdata.com/download/download.aspx?sku=PGZK-V&type=beta
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation that enables interaction with Greenhouse's recruitment and applicant tracking system through Model Context Protocol, providing tools for job listings, candidate management, application filtering, and stage transitions.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools for job search, inbound recruiter activity triage, conversation inbox access, and guarded profile updates.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that automates applying to jobs on Lever and Greenhouse ATS systems. It fills forms from a candidate profile, verifies fields, and supports dry-run or live submission, with optional chat integration via Hermes.
      -

    TDQS

    A3.9/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions include routing hints that clarify when to use each one. Some overlap exists among application-listing tools (list_applications, fetch_new_applications, stale_applications, pipeline_summary) and resume-search tools, but the intended boundaries are mostly clear.

    Naming Consistency4/5

    The majority of tools follow a snake_case verb_noun pattern like list_jobs, get_candidate, and reject_application. A few analytic tools break the pattern (pipeline_summary, source_effectiveness, time_to_hire, candidates_needing_action), and there is some verb variation across list/fetch/search/read, but the overall convention is predictable.

    Tool Count2/5

    33 tools is a heavy surface for an MCP server, exceeding the 25+ threshold where the set becomes difficult for an agent to navigate. While the ATS domain is broad, several tools overlap in capability and could be consolidated or omitted.

    Completeness2/5

    There are significant gaps, including referenced tools that do not exist in the set: list_tags, list_email_templates, and move_application_same_job are mentioned in descriptions but unavailable. There are also no create/update operations for candidates or jobs, and add_tag_to_candidate depends on a missing tag-listing tool, which will cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues