Skip to content

ATS

Greenhouse MCP connector

The Greenhouse connector brings candidates, applications, jobs, job posts, stages, departments and offices into Claude, ChatGPT, Cursor and the Elaichi Agent, so recruiters ask about the pipeline in plain language while every call runs inside their own Greenhouse access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Greenhouse to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Greenhouse once

  1. Open Connections, choose Add connection, and pick Greenhouse.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Greenhouse API key. One person generates a token in Greenhouse and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

greenhouse
Greenhouse
Ashby
Gem
Huntr
Lever
Manatal
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Greenhouse MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Greenhouse MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Greenhouse MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Greenhouse to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Greenhouse through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Recruiting

    Check where a candidate stands before the call

    Ask for a candidate by name and get their open applications, the stage each one sits in, the source they came from and any tags, without opening Greenhouse mid-conversation.

  • Hiring managers

    See every application on my open role

    Pull the applications for one job, grouped by stage, so a hiring manager knows how many people are in onsite versus phone screen before the weekly sync.

  • Talent operations

    Report pipeline health across departments

    List open jobs by department and office, count applications at each stage and spot roles that have gone quiet, then paste the summary straight into the leadership update.

  • Recruiting

    Find out which sources actually deliver

    Compare where applications for a role came from, referral, job board or agency, and see which sources fill the pipeline and which only add noise.

  • People

    Audit who has which Greenhouse role

    List Greenhouse users alongside their user roles to confirm that departed staff, contractors and interviewers hold only the access they should.

  • Workplace

    Keep offices current as the company grows

    Create a new office in Greenhouse when a location opens and update the details of an existing one, so job posts and departments point at the right place.

Try asking

  • “Which Greenhouse jobs have candidates waiting on interview feedback?”
  • “Summarize applications received for the Senior Engineer job post.”
  • “List candidates by source for open Greenhouse departments.”

See all 52 Greenhouse tools below

Compare

Elaichi vs Zapier MCP vs Composio for Greenhouse

All three can connect Greenhouse to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Greenhouse, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Greenhouse tools Allow or restrict single Greenhouse tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Greenhouse call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Greenhouse tools for your AI agents

52 tools are ready to call through Elaichi's MCP endpoint the moment you connect Greenhouse, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Greenhouse gets you

6 screens from the product, each doing one job for your Greenhouse account.

The agent

Ask about candidates, get answers from Greenhouse.

Plain language questions read live Greenhouse jobs, applications and candidate records.

  • candidates
  • jobs
  • applications
  • job posts

Ask Elaichi to work across your apps.

Which Greenhouse jobs have candidates waiting on interview feedback?

Summarize applications received for the Senior Engineer job post.

List candidates by source for open Greenhouse departments.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Greenhouse.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

52 Greenhouse tools ready without custom code.

Candidates, jobs, applications, job posts, departments, users, tags and sources, all covered.

  • List all Greenhouse candidates
  • Get single Greenhouse candidate by ID
  • List all Greenhouse jobs
  • Get single Greenhouse job by ID
ElaichiTools
Tool Action Description
List all Greenhouse candidates List List all candidates in Greenhouse. Returns candidate details including id, first_name, last_name, company, title, created_at, updated_at, applications, educations, employments, and custom fields.
Get single Greenhouse candidate by ID Get Get information about a specific candidate by id in Greenhouse. Returns candidate's personal details, contact info, applications with job details, custom fields, and associated tags.
List all Greenhouse jobs List List all jobs in Greenhouse. Returns job id, name, requisition_id, status, created_at, updated_at, departments, offices, custom_fields, hiring_team, and openings.
Get single Greenhouse job by ID Get Get information about a specific job in Greenhouse by id. Returns job details including name, requisition_id, status, dates, departments, offices, custom fields, hiring team, and openings.
List all Greenhouse applications List List all applications in Greenhouse. Returns application id, candidate_id, prospect status, applied_at, last_activity_at, location, source, credited_to, jobs, status, current_stage, answers, prospect details, custom fields, and attachments.

Toolboxes

Every team gets its own Greenhouse toolbox.

Recruiting sees pipelines, Finance sees offers, each toolbox scoped to one team.

  • Recruiting
  • Hiring managers
  • Talent sourcing
  • People operations
ElaichiToolboxes
Name Source template Tools Created

Recruiting toolbox

Greenhouse · candidates and applications

Greenhouse starter 18 Mar 4, 2026

Hiring managers toolbox

Greenhouse · jobs and interview stages

— 9 Mar 2, 2026

Talent sourcing toolbox

Greenhouse · sources and tags

— 24 Feb 27, 2026

People operations toolbox

Greenhouse · departments and users

Greenhouse starter 6 Feb 19, 2026

Finance toolbox

Greenhouse · offers and headcount

— 31 Jan 30, 2026

Exec toolbox

Greenhouse · pipeline reporting

— 12 Jan 22, 2026

Shared connections

Share a Greenhouse connection, never a credential.

See who connected each account and which teams and members work through it.

  • Recruiting EMEA
  • Recruiting Americas
  • Engineering hiring
  • Sales hiring
ElaichiConnections
Connection Scope Status Access
GR

Greenhouse (Recruiting EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GR

Greenhouse (Recruiting Americas)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GR

Greenhouse (Engineering hiring)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GR

Greenhouse (Sales hiring)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GR

Greenhouse (Campus hiring)

Connected by Ryan Hayes

Personal • Active Not shared
GR

Greenhouse (People ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Greenhouse candidate.

Append-only log of when, who, what happened, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Greenhouse Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Greenhouse Candidates Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Greenhouse Candidates List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a hiring digest ships.

Greenhouse applications are fetched, grouped, drafted by an agent, approved, then posted back.

Greenhouse digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch candidates

    Greenhouse

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Greenhouse

    Queued

Collections and dashboards

Greenhouse hiring numbers, computed and refreshed.

Four metrics, 14 days of candidates created, and a breakdown by team.

Greenhouse health

Refreshed 4 minutes ago · every 15 minutes · from the candidates collection

Live

Candidates

1,284 ↓ 12%

Jobs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Candidates created

Last 14 days

By team

Share of activity

Recruiting EMEA 34%

Recruiting Americas 27%

Engineering hiring 21%

Sales hiring 18%

FAQ

Frequently asked questions

How do I connect Greenhouse to Claude?

Connect Greenhouse in Elaichi first: create an API key inside Greenhouse and paste it into the Greenhouse connector in Elaichi. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and Greenhouse is available in your next conversation.

Does Greenhouse work with ChatGPT and Cursor as well as Claude?

Yes. Once Greenhouse is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Greenhouse once and every client you use picks it up, with the same permissions and the same audit log behind each one.

What can an AI agent actually do with my Greenhouse data?

An agent connected to Greenhouse can look up candidates, applications, jobs, job posts, job stages, sources, tags, departments, offices, users and user roles, and it can create or update an office. In practice that means asking how many applications a role has at each stage, which source a candidate came from, or which users hold the admin role, and getting the answer from live Greenhouse records. Short, specific asks like "applications for the Account Executive role by stage" work better than long paragraphs.

Does connecting Greenhouse give the AI access to every candidate and job?

No. Each person signs in to Elaichi as themselves, and the Greenhouse access an agent uses follows that person and the permissions on the Greenhouse API key they connected. Elaichi can narrow that access further, by hiding actions or limiting a team to a particular set of tools, but it can never widen it beyond what Greenhouse itself already allows.

Can my team share one Greenhouse connection?

Yes. One recruiter or admin connects Greenhouse in Elaichi and shares the connection with a team, and nobody else on that team ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who asked about which candidate or job, even though they all work through one shared Greenhouse connection.

Can I stop an agent from changing things in Greenhouse?

Yes. Restrictions in Elaichi apply per action, so you can allow reading candidates, applications and jobs while blocking the ability to create or update an office in Greenhouse. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however it is worded, can reach it.

What happens to a Greenhouse connection when someone leaves?

When you offboard a person in Elaichi, their access to Greenhouse through every client ends at once, in Claude, ChatGPT, Cursor and the Elaichi Agent alike. A shared Greenhouse connection keeps working for everyone else on the team. If you want to remove Greenhouse entirely, disconnecting it once in Elaichi removes it from every client at the same time.

Does the Greenhouse MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Greenhouse is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Greenhouse?

Yes. Both let Claude, ChatGPT or Cursor use Greenhouse. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Greenhouse call.

How is Elaichi different from Composio for Greenhouse?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Greenhouse: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Greenhouse in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.