Greenhouse MCP connector
The Greenhouse connector brings candidates, applications, jobs, job posts, stages, departments and offices into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so recruiters ask about the pipeline in plain language while every call runs inside their own Greenhouse access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Greenhouse jobs have candidates waiting on interview feedback?
Working in Greenhouse with Elaichi
-
List all Greenhouse candidates
-
Get single Greenhouse candidate by ID
-
List all Greenhouse jobs
How to connect Greenhouse to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Greenhouse MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Greenhouse MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Greenhouse MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Greenhouse MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Greenhouse to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Greenhouse through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Greenhouse is logged.
-
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.”
What connecting Greenhouse gets you
6 screens from Elaichi, each doing one job for your Greenhouse account.
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, Cursor or Microsoft Copilot
The agent
Ask about candidates, get answers from Greenhouse.
Plain language questions read live Greenhouse jobs, applications and candidate records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Greenhouse.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
52 Greenhouse tools ready without custom code.
Candidates, jobs, applications, job posts, departments, users, tags and sources, all covered.
Toolboxes
Every team gets its own Greenhouse toolbox.
Recruiting sees pipelines, Finance sees offers, each toolbox scoped to one team.
Shared connections
Share a Greenhouse connection, never a credential.
See who connected each account and which teams and members work through it.
Audit log
Answer who touched which Greenhouse candidate.
Append-only log of when, who, what happened, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Greenhouse digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch candidates
Greenhouse
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Greenhouse
Queued
Automations
A schedule fires, a hiring digest ships.
Greenhouse applications are fetched, grouped, drafted by an agent, approved, then posted back.
Greenhouse health
Refreshed 4 minutes ago · every 15 minutes · from the candidates collection
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%
Collections and dashboards
Greenhouse hiring numbers, computed and refreshed.
Four metrics, 14 days of candidates created, and a breakdown by team.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 restricting actions or limiting a team to a particular set of tools, but it can never widen it beyond what Greenhouse itself already allows.
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 restricting the ability to create or update an office in Greenhouse. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot