Skip to main content
Book a demo

Connect Greenhouse to Cursor

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

Book a demo Cursor setup guide

Set up

Add Greenhouse to Cursor in four steps

Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Greenhouse’s 156 tools show up in Cursor’s own tool list.

    Cursor 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 Cursor

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

Tools

156 Greenhouse tools in Cursor

Runlayer policy decides which of these Cursor 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 Cursor

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination