Greenhouse MCP
Related Servers
Alternatives to Greenhouse MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProduction-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.33MIT
- AlicenseNot gradedqualityDmaintenanceThis 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=betaMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying and managing Greenhouse recruiting data through MCP, including applications, candidates, jobs, and rejection operations.MIT
- FlicenseNot gradedqualityDmaintenanceA 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-
- AlicenseNot gradedqualityCmaintenanceA 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
- FlicenseNot gradedqualityDmaintenanceFull-coverage, read-only MCP server for the Teamtailor recruitment API. Exposes 18 tools covering candidates, jobs, applications, offers, stages, departments, locations, users, and activities with strict input validation.-
TDQS
Scored across 167 tools
The tool set covers a comprehensive range of Greenhouse operations, but there is significant overlap and ambiguity between similar tools. For example, 'add_attachment' and 'add_attachment_to_application' have unclear distinctions, and 'advance_application', 'move_application_same_job', and 'move_application' require careful reading to differentiate. While descriptions help, the sheer number of tools increases confusion, with many performing similar actions on different entities (e.g., list operations for various resources).
Tool names largely follow a consistent verb_noun pattern (e.g., 'create_candidate', 'list_applications', 'update_job'), which aids predictability. However, there are minor deviations such as 'candidates_needing_action' (noun_verb) and 'source_effectiveness' (noun_noun), and some tools use underscores inconsistently (e.g., 'webhook_setup_guide' vs. 'webhook_create_rule'). Overall, the naming is mostly uniform and readable, with only a few outliers.
With 167 tools, the count is excessive for a single MCP server, making it overwhelming and difficult to navigate. While Greenhouse is a complex platform, the tool set includes many highly specific or redundant operations (e.g., separate tools for listing various entities like 'list_board_degrees' and 'list_degrees'), which could have been consolidated. This bloated count hinders usability and suggests poor scoping, as a more focused set would improve coherence.
The tool set provides exceptionally complete coverage of the Greenhouse domain, encompassing CRUD operations for candidates, applications, jobs, interviews, users, and more, along with advanced features like pipeline analytics, bulk actions, and webhook management. There are no obvious gaps; tools support full lifecycles from prospecting to hiring, including data management, reporting, and integrations. This completeness ensures agents can handle diverse recruiting workflows without dead ends.