Greenhouse MCP
Wire Greenhouse recruiting APIs into your agent so you can manage candidates, jobs, and hiring workflows without clicking through the ATS all day.
Overview
Greenhouse MCP is a Grow-phase MCP server that exposes 175 Greenhouse recruiting tools to agents over stdio for ATS automation.
What is this MCP server?
- Production-oriented Greenhouse MCP server (open-greenhouse-mcp on PyPI)
- Advertised catalog of 175 tools for recruiting-team workflows
- stdio transport for local agent integration via package version 0.3.2
- Targets full ATS surface area rather than a thin read-only job board
- 175 tools advertised for recruiting teams
- Package identifier open-greenhouse-mcp on PyPI, version 0.3.2
- Transport type stdio per server.schema.json
What problem does it solve?
Recruiting teams lose hours context-switching between the IDE and Greenhouse for repetitive ATS tasks.
Who is it for?
Small teams and recruiting leads on Greenhouse who want deep ATS coverage from Claude Code or Cursor via MCP.
Skip if: Solo builders with no ATS, or anyone who only needs essay research or data-validation MCPs.
What do I get? / Deliverables
Agents can call Greenhouse tools from the terminal so reqs, candidates, and pipeline updates stay in one workflow.
- Agent-callable Greenhouse recruiting operations across the advertised 175-tool surface
- Local stdio MCP bridge between your IDE agent and Greenhouse
Recommended MCP Servers
Journey fit
Canonical shelf is Grow because Greenhouse is for scaling the team and hiring lifecycle after the product exists, not for first-pass idea research. Lifecycle fits recruiting operations—open roles, applicants, and pipeline stages—as ongoing growth work rather than launch SEO or ship testing.
How it compares
175-tool Greenhouse ATS MCP over stdio, not a content essay server or auto-discovered data rules engine.
Common Questions / FAQ
Who is io.github.benmonopoli/greenhouse-mcp for?
Recruiting teams and founders using Greenhouse who want agent-driven ATS operations from a local MCP client.
When should I use io.github.benmonopoli/greenhouse-mcp?
Use it during Grow when you are actively hiring and need programmatic Greenhouse access alongside your coding agent.
How do I add io.github.benmonopoli/greenhouse-mcp to my agent?
Install open-greenhouse-mcp from PyPI (v0.3.2), configure stdio MCP in your agent, and supply Greenhouse API credentials per the repo docs.