PlugWiki

Greenhouse MCP server: use your recruiting data in Claude and ChatGPT

OfficialRemote
Gethttps://mcp.us.greenhouse.io/mcpDocs
Works in
3
supported apps
Risk
Medium
can write
Auth
OAuth
sign in, no key

Lets Claude or ChatGPT search and update your Greenhouse candidates, jobs, interviews and offers in plain language.

This is Greenhouse's own server, and it lets Claude, ChatGPT and other approved AI tools work with your live Greenhouse Recruiting data. You can ask about your pipeline, summarize scorecards, find stalled candidates and, if your admin allows it, update records and move applications. It is in open beta for Greenhouse Recruiting Core, Plus and Pro, and a Site Admin has to turn it on and approve each AI tool before anyone can connect. Each person signs in with their own Greenhouse account and only sees what their permissions already allow.

Good for

  • Recruiters who want quick answers on pipelines, stages and stalled candidates
  • Hiring managers who want scorecard and debrief summaries before a decision
  • Recruiting ops teams auditing jobs, interview kits and offer approvals
  • Greenhouse Site Admins who want governed AI access instead of exports

Works in

3 supported · 11 should work

Tap an app to see how to set it up and any known problems.

Install Greenhouse MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Greenhouse MCP server to Claude Code. Run this command:

claude mcp add greenhouse --transport http https://mcp.us.greenhouse.io/mcp

Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Greenhouse Recruiting Core, Plus or Pro, A Site Admin has approved this AI tool in Dev Center > MCP Access.

Read-only mode: Ask your Site Admin to turn on only the read scopes in Dev Center > MCP Access. You can also untick data types on the Greenhouse sign-in screen.

Greenhouse MCP is in open beta. Before anyone can connect, a Site Admin adds this AI tool as a client in Dev Center > MCP Access and picks which data it may reach. Then each person signs in with their own Greenhouse account. To use a sandbox, sign out of Greenhouse before you connect. Run /mcp inside Claude Code to check that greenhouse shows as connected.

From the vendor's docs. Source.

Tools

We don't list Greenhouse MCP's tools here yet. After you connect it, ask your assistant "What can you do with Greenhouse MCP?" to see them.

Pros and cons

Good

  • Made and run by Greenhouse, with nothing to install.
  • Each person signs in with their own account and keeps their existing permissions.
  • Read-only by default until a Site Admin turns on more.
  • Deletes are blocked, and hiring or rejecting needs your confirmation.
  • Covers candidates, jobs, interviews, scorecards, offers and reporting.
  • Every call is audit-logged with the user and the AI tool.

Watch out

  • Still in open beta, so tools and behaviour can change.
  • Only for Greenhouse Recruiting Core, Plus and Pro; pricing goes through your account team.
  • A Site Admin must approve each AI tool before anyone can connect.
  • Two different addresses depending on the AI tool, which is easy to mix up.
  • ChatGPT needs Developer Mode.
  • Access cannot be narrowed to one department through MCP settings.

Permissions

medium risk · 6 things to watch

Medium risk

With write access turned on, the assistant can change candidate records, move applications and submit scorecards, and candidate data ends up in your AI tool. Start with read-only access and check your AI provider's data settings before recruiters connect.

What it can do

Watch out for

  • It can change candidates and move applications

    With write scopes on, it can add notes, update candidates, move applications and submit scorecards. Turn on only read scopes until your team trusts it. support.greenhouse.io

  • Candidate data leaves Greenhouse for your AI tool

    Data the assistant reads, including resumes it opens from download links, is kept under your AI provider's rules. Check those settings and the laws on AI in hiring with your legal team. support.greenhouse.io

  • A password change does not cut off access

    Connections survive a password change or SSO sign-out. Disconnect under Connections in your Greenhouse profile instead. support.greenhouse.io

  • Access cannot be limited to one department

    MCP settings switch whole data types on or off. Use each person's Greenhouse permissions to keep them to their own jobs. support.greenhouse.io

  • Deletes are blocked and big decisions need a yes

    It cannot delete anything. Rejecting, hiring, merging or anonymizing a candidate and bulk permission removals stop for your confirmation. support.greenhouse.io

  • Every action is audit-logged

    Calls are logged with the user and the AI tool. In the Change Log, changes show under the user's name with no AI marker. support.greenhouse.io

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyA Site Admin enables only read scopes in Dev Center > MCP Access; if MCP Access was never configured, Greenhouse applies a default set of read-only list scopes. Users can also untick categories on the consent screen.
Talks tomcp.greenhouse.io. mcp.us.greenhouse.io
Sign-in and keysOAuth with PKCE; the AI tool holds a one-hour access token and a refresh token that expires after 14 days of inactivity.
Data retentionThe Greenhouse server keeps no copy of your data; what the AI tool retrieves follows that tool's own retention rules.

Alternatives

Use Greenhouse's own server if you are on Core, Plus or Pro and your admin can turn it on. Pick open-greenhouse-mcp if you would rather run a server yourself with your own Greenhouse API credentials; the job board scraper only reads public job listings, not your recruiting data.

ServerOfficialRunsSign-inCan change thingsTools
GreenhouseThis pageOfficialHostedAccountYes159
open-greenhouse-mcpCommunityLocalAPI keyYes–
Greenhouse Jobs ScraperCommunityHosted–No–

Questions

What is the Greenhouse MCP server URL?

For a Claude custom connector, use https://mcp.greenhouse.io/mcp. For Claude Code and ChatGPT, Greenhouse's guide uses https://mcp.us.greenhouse.io/mcp.

Is Greenhouse MCP free?

It is in open beta for Greenhouse Recruiting Core, Plus and Pro customers. Greenhouse does not publish a separate price; ask your account team about access and pricing.

Why won't my AI tool connect?

A Site Admin has to add the tool as an approved client in Dev Center, MCP Access before anyone can connect, even for Claude and ChatGPT. Until then, sign-in fails with a redirect address error.

Can it delete candidates or jobs?

No. Greenhouse blocks every delete action. Rejecting, hiring, merging or anonymizing a candidate also stops and asks for your confirmation first.

How do I make it read-only?

A Site Admin turns on only the read scopes in Dev Center, MCP Access. If nobody has set it up yet, Greenhouse already uses a read-only default set. Each person can also untick data types when they sign in.

Can recruiters use it, or only admins?

Anyone on an eligible plan can, once a Site Admin has set it up. Each person signs in with their own account and only reaches what their Greenhouse permissions allow.

Can it read resumes?

It shares a download link for each attachment that lasts seven days, and your AI tool may open it. Admins can turn off the attachments scope to stop that.

Why did some tools disappear after an admin change?

Tools only appear for scopes your admin has turned on. When scopes change, everyone is logged out and has to disconnect and reconnect to get the new set.

How do I connect to my sandbox instead of production?

Sign out of Greenhouse first, then connect and sign in to the sandbox account. The connection uses whichever account you sign in with.

How do I add it to Claude?

In Claude, open Settings, then Connectors, and add a custom connector with the Greenhouse address. Steps for each app are in the install box above.

Examples

  • Find candidates stuck in a stage

    Which candidates for the backend engineer role have been in Onsite for more than two weeks?

    Source

  • Summarize final-round scorecards

    Summarize the scorecards for Priya's final round

    Source

  • Create a new opening

    Create an opening for the new Design Lead role in our London office.

    Source

  • Check scorecard completion across hiring managers

    Source

  • Find offer approval bottlenecks by approver

    Source

Information

updated Nov 1, 2026

Publisher
Official
Endpoint
https://mcp.us.greenhouse.io/mcp
Transport
Streamable HTTP
Auth
OAuth

WebsiteDocsOfficial listingSupport

Other Greenhouse MCP servers

See all

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 6
  1. Set up Greenhouse MCP with supported AI tools · support.greenhouse.io
  2. Greenhouse MCP security FAQ · support.greenhouse.io
  3. Greenhouse connector for Claude · claude.com
  4. Greenhouse MCP · support.greenhouse.io
  5. GitHub · github.com
  6. open-greenhouse-mcp README · raw.githubusercontent.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 1, 2026.