Greenhouse MCP server

Connect Greenhouse to Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini, GitHub Copilot and any other MCP client, for your whole team. Metorial adds security, governance, and tracing, and gives everyone one Magic MCP URL to connect.

Deploy GreenhouseBook a demo

What you can do with the Greenhouse MCP server

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Use the advance or move application tool in Greenhouse
  • Use the list users tool in Greenhouse
  • Use the reject application tool in Greenhouse
  • Use the list scheduled interviews tool in Greenhouse
  • Use the get candidate tool in Greenhouse
  • Use the create candidate tool in Greenhouse

Supported Tools

advance_application

Advance or Move Application

Advance automatically or move to a chosen job interview stage. Stage transition rules can send automated emails and retain history. Read get_application and get_job with includeStages before moving.

list_users

List Users

List users by exact primary email or one date range. This list does not identify the current authenticated user.

reject_application

Reject Application

Reject an application with a required rejection reason. Email scheduling requires a template and timestamp. This operation retains rejection history and may send email; confirmation does not prove email delivery.

list_scheduled_interviews

List Scheduled Interviews

List interviews by application or one date range. Returns timing, status and job interview IDs; expanded v1 interviewer data is unavailable.

get_candidate

Get Candidate

Get Candidate. Uses Harvest v3 permissions and verified resource IDs.

create_candidate

Create Candidate

Create a candidate, optionally with one application. Harvest v3 supports at most one job ID and untyped socialMediaUrls; legacy typed socialMediaAddresses require migration.

get_user

Get User

Get User. Uses Harvest v3 permissions and verified resource IDs.

list_applications

List Applications

List applications by job, candidate, status or one date range. Returns current job interview stage and relationship IDs.

create_job

Create Job

Create a job from an existing template. Harvest v3 requires numberOfOpenings. The API has no job deletion operation; creation leaves a job and audit history.

add_candidate_note

Add Candidate Note

Add a candidate note with the specified author and visibility. There is no individual note deletion operation. Permanent candidate deletion also deletes associated notes; audit history may remain.

list_offices

List Offices

List office names, locations, parent IDs and external IDs. Follow nextCursor to retrieve further results.

get_job

Get Job

Retrieve a job and optionally its complete bounded interview plan. Returns relationship IDs; expanded v1 names, hiring-team details and openings are unavailable.

list_candidates

List Candidates

List candidates by email or one date range. Harvest v3 job filtering is available through list_applications.

list_jobs

List Jobs

List jobs by status, department or office. Returns department and office IDs; expanded v1 relationship names are unavailable.

update_candidate

Update Candidate

Update only the supplied candidate fields. Contact arrays and tags replace their existing values. The authenticated v3 subject controls audit identity.

manage_candidate_tags

Manage Candidate Tags

Add or remove an existing tag on one candidate. Resolves the exact tag name and verifies membership. Does not create or delete organization-wide tag definitions.

list_offers

List Offers

List offers by application, supported status or one date range. sentAt and startsAt are calendar dates. Sent is not a v3 status.

get_application

Get Application

Get Application. Uses Harvest v3 permissions and verified resource IDs.

list_departments

List Departments

List department names, parent IDs and external IDs. Follow nextCursor to retrieve further results.

list_rejection_reasons

List Rejection Reasons

Discover organization rejection reason IDs required by reject_application. Follow nextCursor for further results.

get_current_context

Get Current Context

Verify the current Harvest v3 token with its issuing client. Returns organization, token subject, granted scopes and current role when Greenhouse provides them. The subject may be an integration service account, rather than a person.

list_application_attachments

List Application Files

Discover resumes, cover letters and other files for one application. Use a returned file ID with download_application_attachment. Download links are issued separately.

download_application_attachment

Download Application File

Prepare a downloadable resume, cover letter or other application file. Verifies that the selected file belongs to the application. Greenhouse file links last seven days and can be renewed.

Connect Greenhouse to your AI client

Every client uses the same Magic MCP URL, and so does any other MCP client. Add it once and sign in with SSO.

  1. Enable Greenhouse in Metorial. In your Metorial portal, enable the Greenhouse MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
  2. Add a custom connector. Open Customize, then Connectors. Select Add, then Custom, then Web.
  3. Paste your Metorial MCP URL. Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>) and continue.
  4. Sign in. Select Add and sign in to load Greenhouse tools.

Run Greenhouse through the Metorial gateway

One governed layer for every app your agents reach, not a separate connector per tool.

  • Give Greenhouse and every other app to your whole team through one MCP gateway, behind your SSO.
  • Scope which teams and agents can use Greenhouse tools with role-based access control, and trace every call.
  • Prefer to run it yourself? Metorial is open source and self-hostable.

More integrations teams use with Greenhouse

Linkedin

Authenticate LinkedIn members with OpenID Connect, fetch the authenticated member profile, and create self-serve LinkedIn shares with text, article links, and uploaded images. Organization and Community Management workflows should move to a separate slate because LinkedIn restricts combining those products in one app.

Workable

Manage recruiting, hiring, and HR processes. Create and track job postings, manage candidates through hiring pipelines, and handle employee records. Create, move, disqualify, and comment on candidates. Manage requisitions with approval workflows. Retrieve offers and scheduled events like interviews. Create and manage departments. Handle employee data, documents, and time-off requests. Build custom careers pages with public job listing endpoints.

Ashby

Read and manage candidates, applications, jobs, offer forms and interview schedules. Discover required organization resources, inspect the connected API key and download provider files.

Async Interview

Review asynchronous interview campaigns and candidate submissions. List interview jobs, retrieve interview responses with candidate details and recording links, and filter responses by job.

Bamboohr

Read and update visible BambooHR employee records and tables, time off, timesheets, goals and training records. Discover employee IDs, current reports and active applicant statuses. Read company benefit summaries and employee dependents, retrieve applicant tracking data, generate reports and download employee or company files. Permissions and company configuration determine availability.

Breathe Hr

Read employee, absence, sickness, organization, compensation and training records. Create employee and sickness records, request or decide leave, cancel absences, and manage expenses and claims. Discover the connected account and available configuration records.

Technical notes for Greenhouse

Manage Greenhouse candidates and applications through Harvest v3 OAuth. Create and update candidate records, advance or reject applications, create jobs from templates, and read jobs, offers, interviews, users, departments and offices. Discover rejection reasons, verify the current organization and download application files. Stage changes and rejections can retain history and run configured automation.

Frequently asked questions

Common questions about connecting Greenhouse to AI agents with Metorial.

  1. How many tools does the Greenhouse MCP server have?
    The Greenhouse MCP server exposes 23 tools, including Advance or Move Application, List Users, Reject Application. Each one is governed and traced through Metorial.
  2. Greenhouse exposes tools your agents call on demand; it does not publish event triggers yet. Everything still runs through one governed MCP URL.
  3. Any MCP client, including VS Code, Windsurf, Zed, OpenCode and Grok. Each one reaches the Greenhouse MCP server through the same Metorial URL.
  4. Use role-based access control to decide which teams, users, and agents can use Greenhouse and which of its tools they can call.
  5. Yes. Metorial is open source, so you can run the Greenhouse MCP server yourself or use the hosted gateway.

Connect Greenhouse to production AI agents

See how Metorial gives your team governed access to Greenhouse, with tracing and security controls built in.

Book a demoDeploy Greenhouse