Bring Candidate Tracking
to CrewAI
Learn how to connect Greenhouse to CrewAI 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 CrewAI?
When paired with CrewAI, Greenhouse becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Greenhouse tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Greenhouse in CrewAI
Greenhouse and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Greenhouse to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.