benmonopoli/open-greenhouse-mcp

Production-ready MCP server for Greenhouse, designed for recruiters and hiring teams.
Most Greenhouse MCP servers mirror the API endpoint by endpoint. This one is built for recruiting teams: safe defaults, role-based profiles, and workflow tools that turn multi-step API operations into single actions.
Choose a Profile
| Profile | Tools | Can write? | Recommended for |
|---|---|---|---|
| read-only | 104 | No | First-time setup, reporting, hiring managers |
| recruiter | 128 | Yes (safe ops) | Day-to-day recruiting work |
| full | 187 | Yes (all) | Admins, ops, advanced automation |
> **Harvest v3.** Greenhouse retired Harvest v1/v2 on 31 Aug 2026. From 0.5.0 this server uses Harvest v3 with OAuth 2.0 credentials. Upgrading from 0.4 or earlier? See Migrating from v1/v2.
Quick Start
Add to your MCP client config (Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json, Cursor: Settings > MCP):
Start in read-only mode to validate connectivity and tool behaviour, then switch to recruiter or full when you need write access.
Create the credentials in Greenhouse under **Configure > Dev Center > API Credentials > Create new API credentials > Harvest V3 (OAuth)**, and grant the scopes for the tools you plan to use. The client secret is shown once. See Advanced Setup for how tokens and scopes work.
What You Can Ask
- "Show me the pipeline for our Senior Engineer role"
- "Who needs my attention this week?"
- "What are our conversion rates for the Backend Intern role?"
- "Find Sarah Chen and pull up her resume"
- "Which sources are actually producing hires?"
- "Bulk reject everything inactive for 30+ days on the Account Manager role"
- "Screen this candidate for the Backend Engineer role — give me the full picture"
- "Search our engineering pipelines for anyone with Rust and distributed systems experience"
- "What new applications came in since yesterday?"
See more examples with full output.
See it in action
Safety
- Access is limited by the scopes on your Harvest v3 credential and the acting user's permissions
- Read-only profile is recommended for first setup
- Destructive actions require explicit IDs — the server never infers targets
- Set GREENHOUSE_USER_ID and writes are made as that user (OAuth sub), so Greenhouse's audit trail shows who did what
- Bulk actions are rate-limited to stay within API limits
Compatibility
| Client | Status |
|---|---|
| Claude Desktop | Supported |
| Claude Code | Supported |
| Cursor | Supported |
| Transport | stdio |
| Python | 3.10+ |
Startup
When the server starts, it logs its configuration:
What's Included
- **Screening & sourcing tools** — 6 tools for candidate screening, resume search with boolean keywords, daily digest, and location detection
- **Recruiter workflow tools** — 13 composite tools for pipeline views, analytics, search, and bulk operations
- **Harvest v3 API coverage** — 154 tools across candidates, applications, jobs, offers, interviews, and more
- **Job Board API** — 13 tools for public job listings and application submission
- **Optional webhooks and ingestion** — 14 tools for event-driven workflows and partner integrations
---
Reference
Screening & Sourcing Tools
Tools for candidate evaluation and proactive talent search.
| Tool | What it does |
|---|---|
| screen_candidate | Complete screening package — profile, resume text, location, screening answers, job description, history |