Connect your AI Agents to Greenhouse in minutes

How can I use the Greenhouse MCP server?

Here are just a few use cases:

• Interview scheduling: Your agent can coordinate interview availability by checking candidate responses, reviewing interviewer calendars, and proposing optimal time slots. It can then create the interview in Greenhouse and send calendar invites once approved
  

• Application screening: Your agent can periodically review new applications, extract key qualifications from resumes, and flag high-priority candidates based on predefined criteria. It can also move candidates through pipeline stages and add screening notes automatically
  

• Candidate status updates: Your agent can monitor candidates who haven't received updates in a while and draft status update emails to keep them engaged. For instance, it can detect candidates stuck in a stage for over a week and propose follow-up communications
  

• New hire onboarding prep: Your agent can monitor for accepted offers in Greenhouse and trigger onboarding workflows in your HRIS (e.g., BambooHR, Workday). For example, it can create the employee record in the HRIS, pre-fill details from the candidate profile, and notify IT to start procuring/provisioning equipment and application access
  

• Reference check automation: Your agent can identify candidates ready for reference checks in Greenhouse, extract reference contact details, and initiate reference check requests through your reference checking platform (e.g., Checkr, Xref). Your agent can then log the results back in Greenhouse once the check is complete

What are popular tools for Greenhouse’s MCP server?

Here are just a few popular tools across data types:

Applications

• <code class="blog_inline-code">list_applications</code>
• <code class="blog_inline-code">get_application</code>
• <code class="blog_inline-code">create_application</code>
• <code class="blog_inline-code">advance_application</code>
• <code class="blog_inline-code">reject_application</code>

Candidates

• <code class="blog_inline-code">list_candidates</code>
• <code class="blog_inline-code">get_candidate</code>
• <code class="blog_inline-code">create_candidate</code>
• <code class="blog_inline-code">Add_candidate_note</code>

Jobs

• <code class="blog_inline-code">get_job_stages</code>
• <code class="blog_inline-code">list_job_openings</code>
• <code class="blog_inline-code">create_job_opening</code>
• <code class="blog_inline-code">get_job_approval_flows</code>

What makes Merge Agent Handler’s Greenhouse MCP server better than alternative Greenhouse MCP servers?

Merge Agent Handler provides platform-level capabilities that aren’t inherent to MCP alone:

• Enterprise-grade security and DLP: All tool inputs and outputs are scanned by a security gateway with configurable data loss prevention rules to block, redact, or mask sensitive data
  

• Real-time observability and auditability: Every tool call is logged with a complete, fully-searchable audit trail, enabling teams to debug, review, and manage agent behavior
  

• Managed authentication and permissions: Merge handles dynamic authentication flows, credential storage, and permission validation for registered users, reducing integration complexity
  

• Broad and customizable tool coverage: Merge’s Greenhouse connector comes with 50+ tools out of the box. You can also easily add your own or modify existing ones to fit your exact requirements

Can I set security rules for Greenhouse tool calls in Merge Agent Handler?

Yes, you can set a wide range of security rules for Greenhouse tool calls in Merge Agent Handler. Here are just a few examples:

• Block candidate PII in tickets: Prevent your agents from including candidate social security numbers, home addresses, or phone numbers when creating tickets or notes in other systems based on Greenhouse data

• Redact salary information: Automatically mask compensation details and salary ranges from Greenhouse job requisitions or offer letters before your agents share candidate information across systems

• Log sensitive searches: Track and audit whenever your agents search Greenhouse for candidates with specific demographic information or protected characteristics

• Block external email domains: Prevent your agents from sending candidate data to email addresses outside your organization's domain when drafting outreach messages

• Redact interview feedback: Automatically strip confidential interviewer comments or sensitive evaluation notes before your agents summarize candidate profiles or create reports

• Block unauthorized data exports: Prevent your agents from bulk extracting candidate records or application data that could violate data retention policies

How can I add tools to Merge Agent Handler’s Greenhouse MCP server?

Here are the steps to get started:

1. Create your Agent Handler account. Sign up for a free Merge Agent Handler account here. 

2. Set up a Tool Pack. Navigate to "Tool Packs" in the dashboard sidebar and click "Create New Tool Pack." Add the Greenhouse connector from the list of available MCP connectors and give your Tool Pack a descriptive name (e.g., "Recruiting Automation Pack").

3. Configure authentication. Choose between individual authentication, where each user provides their own Greenhouse credentials, and shared authentication, which uses organization-level credentials for all users.

4. Register a user identity. Navigate to "Registered Users" and create an entry. This represents the identity (either human or system) that’ll perform actions through your agent.

5. Associate the Tool Pack with your agent. Save your Tool Pack and connect it to your agent using the MCP entry URL provided in the Tool Pack settings.