oto.cx
greenhouse

greenhouse

greenhouse.

A Greenhouse candidate — list, read, create, annotate.

ajouter à otoauth : —prefix : greenhouse_*

setup & usage

⚠ your greenhouse (harvest) api key

you need a greenhouse harvest api key.

  • in greenhouse, go to configure → dev center → api credentials and create a key of type *harvest*
  • give it the candidates/jobs/applications/users permissions
  • paste it into your connector keys (or let your org share its own)
  • vendor docs: greenhouse.io
  • ⚠️ writes (creating a candidate, adding a note) require an on_behalf_of = the id of a greenhouse user, retrieved via greenhouse_users
    • ▸ what you can do

    drive your greenhouse ats from the conversation: candidates, jobs, applications, notes.

  • "list the candidates on job 123" → greenhouse_candidate(op="list") (filters job_id, email, created_after)
  • "show me candidate 456 and their applications" → greenhouse_candidate
  • "add a note on candidate 456" → greenhouse_candidate(op="add_note") (needs an author user_id, see greenhouse_users)
  • "which jobs are open?" → greenhouse_job(op="list") (status open/closed/draft)
    • ⚙ multiple comptes

    this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.

  • the first one doesn't need a name; from the second on, each one carries its own (the first then takes the name "principal", renamable)
  • without specification, the agent takes the only stored compte, otherwise the one marked as default; otherwise the call is refused, naming the available comptes — never a random choice
  • target a compte for a call: _account="<name>" on the tool; list them: oto_identity(op='list', connector='greenhouse') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='greenhouse', identity_id='<name>'); rename: op='rename' with new_name
  • ⚠️ no tool walks through the comptes on its own: a total across several comptes is obtained by calling each one (_account) and adding up

    • outils

    chargement…

    utilisation

    claude code — installe le plugin oto — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.
    claude.ai — branche mcp.oto.cx/mcp en connecteur custom (guide)
    cli — pipx install oto-cli puis oto greenhouse …
    ← tous les connecteurscatalogue mcp →