Greenhouse for AI agents
Greenhouse is applicant tracking software that helps recruiting teams manage candidates, jobs, and the hiring pipeline. People teams rely on it to keep employee records accurate without manual double entry. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Greenhouse.
Look up a candidate's status
Pull a candidate's application and interview stage before a recruiter reaches out.
Create a new candidate record
Add a new candidate to the pipeline from a resume or referral, tagged to the right job.
Deactivate a user with approval
Deactivate a recruiter's account only after HR confirms they have left the company.
134 Greenhouse actions, graded by risk.
Every Greenhouse action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
57Look things up. Allowed by default.
- greenhouse.list_eeocList Greenhouse EEOC responses
- greenhouse.list_jobsList Greenhouse jobs
- greenhouse.list_notesList Greenhouse notes
- greenhouse.list_usersList Greenhouse users
- greenhouse.list_offersList Greenhouse offers
- greenhouse.list_officesList Greenhouse offices
- greenhouse.list_sourcesList Greenhouse sources
- greenhouse.list_openingsList Greenhouse openings
- greenhouse.list_approversList Greenhouse approvers
- greenhouse.list_job_notesList Greenhouse job notes
- greenhouse.list_job_postsList Greenhouse job posts
- greenhouse.list_referrersList Greenhouse referrers
- greenhouse.list_candidatesList Greenhouse candidates
- greenhouse.list_interviewsList Greenhouse interviews
- greenhouse.list_job_boardsList Greenhouse job boards
- greenhouse.list_job_ownersList Greenhouse job owners
write
56Create and change things. Allow, or ask the user first.
- greenhouse.create_jobCreate Greenhouse job
- greenhouse.update_jobUpdate Greenhouse job
- greenhouse.create_noteCreate Greenhouse candidate note
- greenhouse.create_userCreate Greenhouse user
- greenhouse.update_userUpdate Greenhouse user
- greenhouse.create_offerCreate Greenhouse offer
- greenhouse.create_officeCreate Greenhouse office
- greenhouse.update_officeUpdate Greenhouse office
- greenhouse.create_openingCreate Greenhouse opening
- greenhouse.update_openingUpdate Greenhouse opening
- greenhouse.create_job_noteCreate Greenhouse job note
- greenhouse.update_job_noteUpdate Greenhouse job note
- greenhouse.create_candidateCreate Greenhouse candidate
- greenhouse.create_interviewCreate Greenhouse interview
- greenhouse.create_job_ownerAdd Greenhouse job owner
- greenhouse.update_candidateUpdate Greenhouse candidate
destructive
21Delete, cancel or archive. Ask first, or deny outright.
- greenhouse.delete_job_noteDelete Greenhouse job note
- greenhouse.delete_candidateDelete Greenhouse candidate
- greenhouse.delete_interviewDelete Greenhouse interview
- greenhouse.delete_job_ownerDelete Greenhouse job owner
- greenhouse.delete_attachmentDelete Greenhouse attachment
- greenhouse.delete_applicationDelete Greenhouse application
- greenhouse.delete_candidate_tagDelete Greenhouse candidate tag
- greenhouse.delete_job_hiring_managerDelete Greenhouse job hiring manager
- greenhouse.delete_blocked_spam_sourceDelete Greenhouse blocked spam source
- greenhouse.delete_candidate_educationDelete Greenhouse candidate education
- greenhouse.delete_custom_field_officeDelete Greenhouse custom field office
- greenhouse.delete_custom_field_optionDelete Greenhouse custom field option
- greenhouse.delete_user_job_permissionDelete Greenhouse user job permission
- greenhouse.delete_candidate_employmentDelete Greenhouse candidate employment
- greenhouse.delete_applied_candidate_tagDelete Greenhouse applied candidate tag
- greenhouse.deactivate_userDeactivate Greenhouse user
Greenhouse in three steps.
- 01Your users connect GreenhouseThey sign in to Greenhouse on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, writes like “create Greenhouse job” can wait for the user, and “delete Greenhouse job note” can be denied outright.
- 03Any agent can actYour agent calls Greenhouse through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('greenhouse', { read: 'allow', write: 'ask', // create_job destructive: 'deny', // delete_job_note }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Greenhouse connects.
Users sign in to Greenhouse on Arc0 Connect and approve the scopes you request. Build with Arc0’s Greenhouse OAuth app, or bring your own so the Greenhouse consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
The same Greenhouse connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0 · OAuth 2.0 client credentials
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Greenhouse from any agent.
Greenhouse and Arc0, answered.
Can I use Greenhouse with Claude, ChatGPT or Cursor?
Yes. Connect Greenhouse to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Greenhouse actions you allow.
How do users connect Greenhouse?
Users sign in to Greenhouse on Arc0 Connect and approve the scopes you request. Build with Arc0’s Greenhouse OAuth app, or bring your own so the Greenhouse consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
Which Greenhouse actions can my agent take?
134 in total: 57 read, 56 write and 21 destructive, such as “create Greenhouse job”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Greenhouse?
Yes. Actions like “delete Greenhouse job note” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Greenhouse too?
Yes. The same Greenhouse connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Greenhouse into your agent.
Your users connect Greenhouse once, under your brand. Your agent gets 134 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan