Connect Greenhouse to Claude Code
Give Claude Code governed access to Greenhouse’s 156 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Greenhouse to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.
- 1
Add Greenhouse to Runlayer
Greenhouse isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Greenhouse’s 156 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code setup guide - 3
Sign in to Greenhouse
Sign in the way Greenhouse requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Greenhouse from Claude Code
Greenhouse’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
156 Greenhouse tools in Claude Code
Runlayer policy decides which of these Claude Code users can call.
Activate user
Reactivate a previously deactivated user so they can sign in to Greenhouse and be assigned to new jobs again.
Add candidate note
Create a candidate note, log an email, or record an activity-feed entry on a candidate.
Bulk activate users
Reactivate up to the bulk-endpoint cap of users in a single request.
Bulk create blocked spam sources
Adds multiple blocked spam sources in a single request, typically used to sync the blocklist from an external security tool.
Bulk create candidates
Asynchronously create many candidate profiles in a single call, typically for HRIS sync workflows that create a batch of candidates at once.
Bulk create custom field options
Asynchronously add many options at once, typically for HRIS sync workflows that replace or extend a dropdown's option set in a single pass.
Bulk create jobs
Asynchronously create many jobs in a single call, typically for HRIS sync workflows that open a batch of requisitions at once.
Bulk create openings
Asynchronously add many openings across one or more jobs in a single call, typically for HRIS sync workflows that open or extend headcount on a batch of requisitions.
Control
What Runlayer can see and stop in Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every Greenhouse call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more