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.

HR and recruitingOAuth 2.0MCP + RESTgreenhouse.io
AUDIT LOG · GREENHOUSEPOLICY: acme-support
09:41:07 · claude · u_8f2read
greenhouse.list_eeoc
List Greenhouse EEOC responses✓ allowed · 212ms
09:41:08 · claude · u_8f2read
greenhouse.list_jobs
List Greenhouse jobs✓ allowed · 164ms
09:41:09 · claude · u_8f2write
greenhouse.create_job
Create Greenhouse job✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
greenhouse.delete_job_note
Delete Greenhouse job note✕ blocked · policy: deny
EVERY GREENHOUSE CALL, ON THE RECORD
01 · USE CASES

What agents do in Greenhouse.

01

Look up a candidate's status

Pull a candidate's application and interview stage before a recruiter reaches out.

02

Create a new candidate record

Add a new candidate to the pipeline from a resume or referral, tagged to the right job.

03

Deactivate a user with approval

Deactivate a recruiter's account only after HR confirms they have left the company.

02 · ACTIONS

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

57

Look things up. Allowed by default.

  • greenhouse.list_eeoc
    List Greenhouse EEOC responses
  • greenhouse.list_jobs
    List Greenhouse jobs
  • greenhouse.list_notes
    List Greenhouse notes
  • greenhouse.list_users
    List Greenhouse users
  • greenhouse.list_offers
    List Greenhouse offers
  • greenhouse.list_offices
    List Greenhouse offices
  • greenhouse.list_sources
    List Greenhouse sources
  • greenhouse.list_openings
    List Greenhouse openings
  • greenhouse.list_approvers
    List Greenhouse approvers
  • greenhouse.list_job_notes
    List Greenhouse job notes
  • greenhouse.list_job_posts
    List Greenhouse job posts
  • greenhouse.list_referrers
    List Greenhouse referrers
  • greenhouse.list_candidates
    List Greenhouse candidates
  • greenhouse.list_interviews
    List Greenhouse interviews
  • greenhouse.list_job_boards
    List Greenhouse job boards
  • greenhouse.list_job_owners
    List Greenhouse job owners
+ 41 MORE

write

56

Create and change things. Allow, or ask the user first.

  • greenhouse.create_job
    Create Greenhouse job
  • greenhouse.update_job
    Update Greenhouse job
  • greenhouse.create_note
    Create Greenhouse candidate note
  • greenhouse.create_user
    Create Greenhouse user
  • greenhouse.update_user
    Update Greenhouse user
  • greenhouse.create_offer
    Create Greenhouse offer
  • greenhouse.create_office
    Create Greenhouse office
  • greenhouse.update_office
    Update Greenhouse office
  • greenhouse.create_opening
    Create Greenhouse opening
  • greenhouse.update_opening
    Update Greenhouse opening
  • greenhouse.create_job_note
    Create Greenhouse job note
  • greenhouse.update_job_note
    Update Greenhouse job note
  • greenhouse.create_candidate
    Create Greenhouse candidate
  • greenhouse.create_interview
    Create Greenhouse interview
  • greenhouse.create_job_owner
    Add Greenhouse job owner
  • greenhouse.update_candidate
    Update Greenhouse candidate
+ 40 MORE

destructive

21

Delete, cancel or archive. Ask first, or deny outright.

  • greenhouse.delete_job_note
    Delete Greenhouse job note
  • greenhouse.delete_candidate
    Delete Greenhouse candidate
  • greenhouse.delete_interview
    Delete Greenhouse interview
  • greenhouse.delete_job_owner
    Delete Greenhouse job owner
  • greenhouse.delete_attachment
    Delete Greenhouse attachment
  • greenhouse.delete_application
    Delete Greenhouse application
  • greenhouse.delete_candidate_tag
    Delete Greenhouse candidate tag
  • greenhouse.delete_job_hiring_manager
    Delete Greenhouse job hiring manager
  • greenhouse.delete_blocked_spam_source
    Delete Greenhouse blocked spam source
  • greenhouse.delete_candidate_education
    Delete Greenhouse candidate education
  • greenhouse.delete_custom_field_office
    Delete Greenhouse custom field office
  • greenhouse.delete_custom_field_option
    Delete Greenhouse custom field option
  • greenhouse.delete_user_job_permission
    Delete Greenhouse user job permission
  • greenhouse.delete_candidate_employment
    Delete Greenhouse candidate employment
  • greenhouse.delete_applied_candidate_tag
    Delete Greenhouse applied candidate tag
  • greenhouse.deactivate_user
    Deactivate Greenhouse user
+ 5 MORE
03 · HOW IT WORKS

Greenhouse in three steps.

  1. 01Your users connect GreenhouseThey sign in to Greenhouse on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create Greenhouse job” can wait for the user, and “delete Greenhouse job note” can be denied outright.
  3. 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.
POLICY.TS
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
04 · AUTH AND DATA

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
05 · WORKS WITH

Use Greenhouse from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Greenhouse and Arc0, answered.

Q01

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.

Q02

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.

Q03

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.

Q04

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.

Q05

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.

Get started

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