Skip to main content
Glama
Sign In
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Greenhouse MCP

No user-submitted related servers found.

    Related Servers

    • open-greenhouse-mcp

      Comradery64
      A
      license
      A
      quality
      A
      maintenance
      Production-ready MCP server for Greenhouse ATS that provides comprehensive recruitment tools—screening, pipeline analytics, search, and safe write operations—across read-only, recruiter, and full profiles.
      33
      MIT

    • Greenhouse MCP

      sam-vangelos
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables recruiters and hiring operators to work inside the Greenhouse applicant tracking system from MCP clients, with per-user permission-scoped reads and a preview/apply flow for safe, auditable writes.
      6 npm
      MIT
    • Greenhouse MCP Server by CData by CDataSoftware

      Greenhouse MCP Server by CDataofficial

      CDataSoftware
      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

    • Greenhouse MCP Server

      Motta239
      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
      -
    • Yardstick ATS MCP Server by yardstickinc

      Yardstick ATS MCP Serverofficial

      yardstickinc
      A
      license
      Not graded
      quality
      C
      maintenance
      A hosted, OAuth-authenticated MCP endpoint exposing 176 tools that let AI assistants read and write jobs, candidates, applications, interviews, scorecards, prospects, talent pools, and imports within an organization's own applicant tracking data, scoped to the signed-in user's existing permissions.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 187 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as multiple candidate search/scan tools (search_candidates_by_name, search_candidates_by_email, list_candidates, scan_all_candidates, search_pipeline_candidates, scan_pipeline_resumes) and overlapping analytics (pipeline_metrics vs source_effectiveness, candidates_needing_action vs stale_applications). Descriptions provide cross-references and clarifications, but the sheer volume and similarity of some tools still create misselection risk.

    Naming Consistency4/5

    Tool names mostly follow a consistent snake_case verb_noun pattern (e.g., list_jobs, get_candidate, create_application, update_interview). A few exceptions exist, such as noun-phrase names (pipeline_summary, candidates_needing_action) and prefixed families (webhook_*, board_*), but the overall convention is predictable and readable.

    Tool Count1/5

    187 tools is an extreme mismatch for a single MCP server, far exceeding the 50+ threshold that indicates poor scoping. Many tools are thin CRUD wrappers or context-specific duplicates (e.g., board vs internal vs ingestion versions) that could be consolidated into fewer, more versatile tools.

    Completeness5/5

    The tool surface covers the entire Greenhouse ATS domain comprehensively: candidates, applications, jobs, interviews, offers, approvals, users, departments, offices, custom fields, tags, sources, rejection reasons, EEOC, webhooks, and ingestion. CRUD lifecycle operations are present for most resources, with no obvious dead ends for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources