3,400+ MCP servers ready to use
Vinkius

Bring Candidate Tracking
to Claude Code

Learn how to connect Greenhouse to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Advance ApplicationCreate CandidateGet Api StatusGet Candidate DetailsGet Job DetailsList ApplicationsList CandidatesList DepartmentsList OfficesList Open JobsReject ApplicationUpdate Candidate
Use with Your AI Agent
Ask AI about this MCP Server
ChatGPT Claude Perplexity

What is the Greenhouse MCP Server?

Connect your Greenhouse account to any AI agent and take full control of your hiring pipeline and recruitment workflows through natural conversation.

What you can do

  • Candidate Orchestration — List and manage candidate records programmatically, including contact info, current company, and professional titles
  • Application Lifecycle — Monitor job applications and take immediate action by advancing candidates to the next stage or marking rejections with reasons
  • Job Management — Access detailed metadata for all active job openings, including hiring teams and department structures
  • Organizational Visibility — Retrieve complete company department lists and office locations to coordinate recruitment logistics
  • System Monitoring — Check API connectivity and Harvest API status directly through your agent for reliable data operations

How it works

1. Subscribe to this server
2. Retrieve your Harvest API Key from Greenhouse (Configure > Dev Center > API Credential Management)
3. Note a valid User ID to perform actions 'On-Behalf-Of' for auditing purposes
4. Start managing your talent acquisition from Claude, Cursor, or any MCP client

No more manual status updates or digging through candidates in the ATS. Your AI acts as your dedicated recruitment coordinator.

Who is this for?

  • Recruiters & Sources — instantly identify candidate statuses and advance top talent through the pipeline using natural language
  • Hiring Managers — retrieve job opening details and department structures without leaving your planning tools
  • HR Operations — manage office locations and department organization through automated queries

Built-in capabilities (12)

advance_application

Move candidate to next stage

create_candidate

Can include first name, last name, and company. Add new candidate

get_api_status

Get account connectivity

get_candidate_details

Get candidate info

get_job_details

Get job metadata

list_applications

List job applications

list_candidates

List recruitment candidates

list_departments

List company departments

list_offices

List office locations

list_open_jobs

List active job openings

reject_application

Requires a reason ID. Reject job application

update_candidate

Modify candidate info

Why Claude Code?

Claude Code registers Greenhouse as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Greenhouse data drives decisions without human intervention.

  • —

    Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • —

    Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • —

    Claude Code runs headlessly, enabling unattended batch processing using Greenhouse tools in cron jobs or deployment scripts

  • —

    Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Greenhouse in Claude Code

AI Agent→Vinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Greenhouse and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Greenhouse to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Use with Your AI Agent View step-by-step setup guide for Claude Code →
Enterprise Security

Why teams choose Vinkius for Greenhouse in Claude Code

The Greenhouse MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Use with Your AI Agent View full Greenhouse details →
Greenhouse
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Greenhouse for Claude Code

Every tool call from Claude Code to the Greenhouse MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

What is the 'On-Behalf-Of' requirement?

Greenhouse requires write operations to be associated with a specific User ID for auditing. This ID is passed in the header to identify who performed the action.

02

Can I search for candidates by email?

Yes! Use the list_candidates tool and provide the email parameter to find a specific person's recruitment record and history.

03

How do I advance an application to the next stage?

The advance_application tool requires a valid application ID. It will automatically move the candidate to the next sequential stage defined in your job's workflow.

04

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable