Bring Candidate Tracking
to AutoGen
Learn how to connect Greenhouse to AutoGen and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
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)
Move candidate to next stage
Can include first name, last name, and company. Add new candidate
Get account connectivity
Get candidate info
Get job metadata
List job applications
List recruitment candidates
List company departments
List office locations
List active job openings
Requires a reason ID. Reject job application
Modify candidate info
Why AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Greenhouse tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Greenhouse tools to solve complex tasks
- —
Role-based architecture lets you assign Greenhouse tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive Greenhouse tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes Greenhouse tool responses in an isolated environment
Greenhouse in AutoGen
Greenhouse and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Greenhouse to AutoGen 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Greenhouse in AutoGen
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 AutoGen 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.
* 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
How Vinkius secures
Greenhouse for AutoGen
Every tool call from AutoGen to the Greenhouse MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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.
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.
How does AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Greenhouse tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"