Greenhouse MCP: setup, scopes and limits
The short answer
Greenhouse MCP is Greenhouse’s official MCP server, in open beta since July 2026 for customers on the Core, Plus and Pro tiers. A Site Admin connects it first and chooses, in Dev Center → MCP Access, which scopes AI tools may use. Other users then connect their own AI tool with their own Greenhouse login and see only what their role allows. By default it can only read applications, candidates, jobs, stages, rejection reasons, scorecards and users. Admins can allow it to add notes, move applications, update candidates and submit scorecards. Greenhouse blocks every delete and asks a person to confirm before an applicant is rejected or hired.
Every Greenhouse detail comes from Greenhouse’s own documentation, read on 1 October 2026. Beatview is not affiliated with Greenhouse.
Greenhouse MCP at a glance
| What the documentation says | |
|---|---|
| Status | Open beta since July 2026 (announced 7 May 2026); Greenhouse says it is not yet generally available |
| Plans | Greenhouse Core, Plus and Pro. Legacy tiers are not eligible. No separate price is published; Greenhouse points to your account team |
| Server address | https://mcp.greenhouse.io/mcp for Claude and Google Antigravity; https://mcp.us.greenhouse.io/mcp for Claude Code and ChatGPT |
| Sign-in | OAuth 2.0 with PKCE. Every user signs in with their own Greenhouse account; no API key |
| Who can connect | A Site Admin sets it up. Since August 2026, Job Admins, recruiters, coordinators and hiring managers can connect their own AI tool |
| AI tools | Pre-approved: Claude, ChatGPT, Google Antigravity, Amazon Q, Glean and Grok. Others work once a Site Admin adds their redirect URL |
| Read by default | Applications, candidates, interview stages, jobs, rejection reasons, scorecards and users |
| Can change, if allowed | Create notes, move applications between stages, update candidate records and submit scorecards |
| Safeguards | Deletes are always blocked. Rejecting or hiring an applicant, merging or anonymizing a candidate and bulk-revoking permissions need a person to confirm |
| Hosting | US infrastructure only; there is no EU endpoint |
What a Site Admin sets up in Greenhouse
Greenhouse makes a Site Admin go first. The scopes they choose are a ceiling no user can go above.
- 01
Step 01
Check you are eligible
You need a Core, Plus or Pro tier, the Site Admin role, and a browser that allows redirects and pop-ups. - 02
Step 02
Choose the scopes
Go to Dev Center → MCP Access, review the scopes, turn on the ones AI tools may use and save. If you never save the page, read-only defaults apply; saving with nothing selected removes all MCP access. - 03
Step 03
Allow the AI tool
Pre-approved tools work as they are. For any other tool, add it under Dev Center → MCP Access → Clients with its redirect URL pattern. - 04
Step 04
Connect your own AI tool
The Site Admin connects first from a supported AI tool, then other users on eligible tiers can authorize their own. - 05
Step 05
Plan for reconnects
Changing scopes ends every active MCP session in the organization, so users reconnect to pick up the new scopes.
Connect Greenhouse to your AI assistant
Steps as Greenhouse documents them for each tool. Use the server address Greenhouse gives for that tool.
Claude
- Open Customize → Connectors, click + and choose Add custom connector. (Greenhouse’s article calls the menu Settings → Connectors.)
- Name it Greenhouse and paste https://mcp.greenhouse.io/mcp, then click Add.
- Click Connect, sign in to Greenhouse and click Authorize.
Claude: custom connectors work on Free (one connector), Pro, Max, Team and Enterprise. On Team and Enterprise, an Owner adds or enables the connector first, and each person then signs in with their own account.
Claude Code
- Run: claude mcp add greenhouse --transport http https://mcp.us.greenhouse.io/mcp
- Finish the sign-in in the browser window that opens.
- Check the connection with /mcp.
ChatGPT
- Turn on developer mode, then open your profile → Apps → Create.
- Name it Greenhouse and enter https://mcp.us.greenhouse.io/mcp as the MCP server URL.
- Leave authentication on OAuth, accept the terms and click Create.
- Sign in to Greenhouse and click Authorize; Greenhouse then shows as enabled.
ChatGPT: OpenAI documents developer mode and custom MCP apps for Business, Enterprise and Edu workspaces, on the web. Only admins and owners can turn on developer mode and publish an app.
Google Antigravity
- Open Settings → MCP Tools and add a server with https://mcp.greenhouse.io/mcp, then save.
- If no sign-in window opens, run /mcp auth greenhouse.
- Sign in to Greenhouse and click Authorize.
What Greenhouse’s MCP server can read and change
Greenhouse exposes part of its Harvest v3 API and publishes no tool list; the MCP Access page in your account is the reference. This is what its help centre documents.
| Area | Read | Change |
|---|---|---|
| Candidates and applications | Candidate and application records; attachment details with a download link that expires after 7 days; Talent Matching AI opt-out status | Update candidate records, add notes and move applications between stages. Rejecting needs a person to confirm |
| Jobs and stages | Jobs, interview stages and rejection reasons | Greenhouse’s use-case examples include updating job custom fields such as priority |
| Scorecards and interviews | Scorecards, and since September 2026 Greenhouse Notetaker transcripts and recording links | Submit scorecards |
| Users | Users | Bulk-revoking permissions needs a person to confirm |
Not documented, so plan without it
- Creating jobs
- Sending emails to candidates
- Creating offers or scheduling interviews
- Returning attachment file contents (only a link that expires)
Greenhouse MCP limits, permissions and audit
Limits to know
- It is an open beta: capabilities are still changing, and Greenhouse publishes no per-tool changelog.
- It runs on US infrastructure only, with no EU endpoint.
- Every request is rate-limited, but Greenhouse doesn’t publish the MCP numbers.
- There is no department or division scoping in the MCP settings; access follows each user’s Greenhouse permissions.
- Changing scopes ends every active MCP session in the organization.
- Greenhouse’s pages give two server addresses, and the security FAQ names only mcp.us.greenhouse.io.
Permissions and audit
- Three layers of control: the Site Admin’s scope ceiling, what each user agrees to at sign-in, and that user’s Greenhouse role.
- Each user gets their own token and shared credentials are rejected, so every action traces back to one person.
- Access tokens last about an hour; refresh tokens expire after 14 days without use.
- MCP calls appear in the Greenhouse Audit Log tagged mcp_access. Querying them through the API needs the Audit Log add-on.
- Users can disconnect from their profile → Connections, and deactivating a user ends their tokens. There is no admin screen to revoke one person’s token.
- Greenhouse says the MCP server stores no prompts or conversations.
What Greenhouse suggests using MCP for
Paraphrased from Greenhouse’s use cases by role. Greenhouse advises starting with read-only questions before allowing changes.
- “Flag candidates who have been in the same stage for more than 10 days.”
- “Which hiring managers still owe scorecards?”
- “Show offers waiting on approval and which approver is the bottleneck.”
- “Summarize the debrief for this candidate from their scorecards.”
- “Which open jobs are missing a job description?”
- “Flag candidates whose salary expectations are above the band midpoint.”
Greenhouse gives your assistant the records. Beatview adds the screening.
Greenhouse MCP lets an assistant search and update your Greenhouse records. Beatview’s MCP server adds the work that happens before anyone’s first call: every applicant scored against your criteria with the reasons shown, and a structured AI video interview assessed answer by answer. Connect both and one assistant can compare what Greenhouse holds with what Beatview found.
One address
Add https://platform.beatview.ai/mcp to Claude, ChatGPT, Gemini or Cursor, next to Greenhouse. It is included on every Beatview plan, including Free.
Evidence, not just records
Beatview returns each applicant’s resume match score with reasons and a structured AI interview assessed answer by answer.
You stay in charge
The assistant confirms with you before moving a candidate or sending an interview invitation, and recordings never leave Beatview.
Try with both connected
- “Which Account Manager candidates scored above 80 in the Beatview interview, and what stage are they at in Greenhouse?”
- “Brief me on Maya Chen: her Beatview interview assessment and the scorecards in Greenhouse.”
- “Who finished the Beatview interview this week but hasn’t moved in Greenhouse yet?”
Greenhouse MCP: frequently asked questions
Still deciding?
Bring a live vacancy and we’ll walk through where automation ends and recruiter review begins.
Yes. Greenhouse MCP is Greenhouse’s official MCP server, in open beta since July 2026 for Core, Plus and Pro customers. It connects Claude, ChatGPT, Google Antigravity and other OAuth tools to Greenhouse Recruiting, within the scopes a Site Admin allows.
Greenhouse’s setup guide uses https://mcp.greenhouse.io/mcp for Claude and Google Antigravity, and https://mcp.us.greenhouse.io/mcp for Claude Code and ChatGPT. Its security FAQ says the server is hosted at mcp.us.greenhouse.io.
It is available on the Core, Plus and Pro tiers, and legacy tiers are not eligible. Greenhouse doesn’t publish a separate price; it asks customers to contact their account team about access and pricing.
Only with a person’s confirmation. Greenhouse requires explicit confirmation before rejecting or hiring an applicant, merging or anonymizing a candidate, or bulk-revoking permissions, and it blocks every delete action.
A Site Admin sets it up and chooses the scopes. Since August 2026, other users on eligible tiers, such as Job Admins, recruiters, coordinators and hiring managers, can connect their own AI tool and see only what their Greenhouse role allows.
No. Greenhouse says the MCP server runs on US infrastructure and there is no separate EU endpoint, so personal data accessed through it is processed in the US.
Yes. Add both servers to the same assistant. Greenhouse supplies your ATS records; Beatview’s MCP server supplies AI resume screening results and structured interview assessments, on every Beatview plan including Free.
Where these details come from
Greenhouse’s own documentation and each AI assistant’s help centre, read on 1 October 2026. MCP servers change quickly; check the source before you rely on a detail.
- Greenhouse MCP
- Set up Greenhouse MCP with supported AI tools
- Greenhouse MCP security FAQ
- Greenhouse MCP use cases by role
- Greenhouse release notes: August 2026
- Greenhouse release notes: September 2026
- Greenhouse launches MCP (press release)
- Claude Help Center: custom connectors using remote MCP
- OpenAI Help Center: developer mode and MCP apps in ChatGPT
Beatview publishes this guide and runs its own MCP server, which works alongside Greenhouse. Where Greenhouse does not document something, we say so rather than guess. Spotted a change? Tell us.