Skip to main content
Book a demo

Connect Greenhouse to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Greenhouse’s 156 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot CLI setup guide

Set up

Add Greenhouse to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.

  1. 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. 2

    Connect GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Greenhouse’s 156 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 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. 4

    Use Greenhouse from GitHub Copilot CLI

    Greenhouse’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

156 Greenhouse tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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.

See all 156 Greenhouse tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Greenhouse call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination