Greenhouse MCP. Manage candidate data and job pipelines via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Greenhouse MCP Server manages your entire recruiting pipeline. Use your AI client to list candidates, track application statuses, and audit job configurations directly.
Get instant access to candidate profiles, department structures, and user access levels—all through conversation, no manual dashboard clicking required.
What your AI agents can do
Create candidate
Adds a new candidate profile into Greenhouse.
Get application
Retrieves all details for a specific job application.
Get candidate
Gets specific profile details for a single candidate.
Retrieves detailed profiles for specific candidates or lists all candidates in your system using get_candidate and list_candidates.
Lists all job applications and checks the current status of a candidate in a specific role using list_applications and get_application.
Retrieves details for specific job postings or lists all active jobs and their associated hiring stages using get_job and list_job_stages.
Lists all company offices and department names to ensure your hiring data matches your organizational structure using list_offices and list_departments.
Retrieves details for specific users or lists all users and their access levels within Greenhouse using get_user and list_users.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Greenhouse MCP Server: 12 Tools for Recruiting Pipeline Management
Use these 12 tools to query and manage core data entities in Greenhouse, from candidates and applications to job postings and users.
019d75abcreate candidate
Adds a new candidate profile into Greenhouse.
019d75abget application
Retrieves all details for a specific job application.
019d75abget candidate
Gets specific profile details for a single candidate.
019d75abget job
Retrieves full details for a single job posting.
019d75abget user
Gets specific profile details for a single user within Greenhouse.
019d75ablist applications
Retrieves a list of all job applications in your system.
019d75ablist candidates
Lists every candidate profile currently stored in Greenhouse.
019d75ablist departments
Lists all active company departments in your organization.
019d75ablist job stages
Lists all defined hiring stages for a particular job posting.
019d75ablist jobs
Lists all active job postings currently set up in Greenhouse.
019d75ablist offices
Lists every physical office location registered in Greenhouse.
019d75ablist users
Lists all user accounts and their roles within Greenhouse.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Greenhouse, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Greenhouse MCP Server lets your AI client manage your whole recruiting pipeline. You'll use natural conversation to list candidates, check application statuses, and audit job settings right from your chat window. You don't gotta click around in a dashboard to get this info.
Find and update candidate details: You can get specific profile details for a candidate using get_candidate, or you can list every candidate profile in your system with list_candidates.
Track application status across jobs: You'll list all job applications using list_applications, and you can check the current status of a candidate in a specific role by getting all details for that application with get_application.
Manage and audit job postings: You can get full details for a single job posting with get_job, and you can list all active jobs and their associated hiring stages using list_jobs and list_job_stages.
Verify company structure: You can list every physical office location using list_offices, and you can list all active company departments using list_departments to make sure your hiring data matches up with your company structure.
Manage user access and roles: You'll list all user accounts and their roles with list_users, or you can get specific profile details for one user using get_user.
How Greenhouse MCP Works
- 1 Subscribe to the server and enter your Greenhouse Harvest API Key (v1/v2).
- 2 Tell your AI client what you need (e.g., 'Show me the applications for the Product Designer job').
- 3 The agent runs the necessary tools (
list_applications,get_application), and you get the structured data back in the chat.
The bottom line is that your AI client acts as a direct interface to Greenhouse, letting you run complex reports and data checks via conversation.
Who Is Greenhouse MCP For?
Recruiters who need to find candidates and verify application statuses without clicking through dashboards. Hiring Managers who need to audit job stages and review profiles directly in chat. HR Operations staff managing office/department lists and verifying user access levels.
Searches for candidates using list_candidates and verifies application statuses with get_application without leaving the chat window.
Reviews job stages using list_job_stages and audits candidate profiles with get_candidate to keep hiring processes moving.
Manages company structure by listing offices (list_offices) and verifying user roles across departments using list_users.
What Changes When You Connect
- See all candidates instantly with
list_candidates. You skip the dashboard, get the list right away, and start searching. - Track application status immediately. Use
list_applicationsandget_applicationto see where a candidate stands without manual navigation. - Audit job structures easily. Check job details with
get_joband list stages withlist_job_stagesto confirm the right hiring steps are in place. - Keep company data clean. Use
list_officesandlist_departmentsto verify that job postings and candidates match your current corporate structure. - Maintain security and compliance. Run
list_usersandget_userto verify who has access and what their roles are in the Greenhouse system. - Build profiles on the fly. Use
get_candidateto pull deep data on a specific person, allowing you to review their history without leaving your agent.
Real-World Use Cases
A recruiter needs to quickly source and verify a top candidate.
A recruiter identifies a strong lead but needs to verify their application status. Instead of logging into the dashboard, they ask their agent: 'What's the status for Candidate ID 93021?' The agent runs get_candidate and get_application, immediately confirming the candidate's current stage and job details.
Hiring manager needs to review job stages for a new role.
A hiring manager is about to post a new job. They ask the agent to list the stages for the 'Product Designer' role. The agent uses list_job_stages and provides the complete, required workflow steps, ensuring no critical review stage is missed before launch.
HR Ops needs to ensure data alignment across departments.
HR Ops must confirm that all open jobs map to active departments. They prompt the agent to cross-reference list_jobs with list_departments. The agent runs both tools, generating a clear report that highlights any jobs linked to inactive or incorrect departments.
Team needs to onboard a new user and set up their profile.
The team needs to create a new user account and link them to an existing job. They use create_candidate to build the profile and then get_user to verify the account access, completing the onboarding process entirely through conversation.
The Tradeoffs
Forgetting the difference between list and get
Asking the agent to 'show me all jobs' and then later asking 'show me the job details.' This results in two separate, manual tool calls and potential confusion about which job ID was used.
→
Use list_jobs first to get the list of IDs, and then use those specific IDs with get_job in a single, chained prompt. This keeps the context tight and ensures you're working with the correct job.
Ignoring company structure tools
Assuming a job posting automatically links to the correct department and office. This leads to data errors when the posting is manually updated outside of the core system.
→
Always run list_departments and list_offices first. This verifies the available company structure data points before you even start creating or reviewing job postings.
Trying to update records without a clear ID
Asking the agent to 'update the candidate's status' without specifying the candidate ID or application ID. The system fails because it doesn't know which record to modify.
→
Always start by running list_candidates or list_applications to get the precise ID. Then, feed that ID back into the agent when you ask it to perform an action.
When It Fits, When It Doesn't
Use this server if your team needs to check, list, or read data across multiple Greenhouse modules (candidates, applications, jobs, users) without opening a browser. It’s best for auditing, reporting, and initial data retrieval.
Don't use this if you need to build complex, multi-step automation that involves custom business logic outside of Greenhouse’s standard flow (like sending an external email or running payroll). For that, you need a dedicated workflow automation platform. This server is pure data access; it doesn't execute actions outside of Greenhouse's boundaries.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Greenhouse. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 12 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Gathering a full candidate profile used to take three different tabs.
Today, finding a candidate's full history is a mess. You start in the candidate tab, grab their contact info. Then, you have to switch to the applications tab to see which jobs they applied for. Next, you jump to the job details page to check the department and the hiring stages. It's copy-pasting IDs and switching between tabs until your eyes hurt.
With the Greenhouse MCP Server, you just ask your agent: 'Give me the profile and application history for Candidate ID 93021.' The agent runs `get_candidate` and `list_applications` in the background. You get all the data—profile, job status, department—in one clean response.
List Jobs and List_Job_Stages: What you get is a clear workflow.
When launching a new role, you used to manually check the job template to confirm the right stages were set. If you missed a step—like 'Portfolio Review'—the job was live but broken. You had to manually check the job configuration against the department's standard flow.
Now, you ask the agent to list the job stages for the new role. The agent uses `list_job_stages` and returns the exact, current, mandatory list. You know immediately if a step is missing or misconfigured. It’s that simple.
Common Questions About Greenhouse MCP
How do I use the Greenhouse MCP Server to list all candidates? +
You run the list_candidates tool. This tool immediately pulls a list of every candidate in your system, giving you a quick overview of your talent pool without any dashboard navigation.
What is the difference between `get_job` and `list_jobs`? +
list_jobs gives you a list of all active job IDs. You must then use get_job and provide a specific ID to retrieve the full, detailed data for one job posting.
Can I see the hiring stages for a specific job using the Greenhouse MCP Server? +
Yes, use list_job_stages. You provide the job ID, and the server returns the complete, sequential list of stages for that specific role.
Does `get_user` require an ID? +
Yes. get_user needs a specific user ID to pull details. It cannot retrieve a user profile without that identifier.
How do I check if a department exists in Greenhouse? +
Run list_departments. This lists all active departments, allowing you to verify the company's current structure before assigning jobs or users.
How does the `create_candidate` tool work if I already have a profile? +
The create_candidate tool will fail if a candidate already exists. You should use get_candidate first to check for the profile ID, then use the ID for subsequent actions.
What information do I get when I run `list_departments`? +
It returns a list of all company departments. Each entry includes the department name and its unique internal ID, which you need for accurate data referencing.
Can I use `get_application` to find out who applied for a job? +
Yes, get_application retrieves the full details for a specific application ID. This data includes the candidate's name, the date of application, and the current job ID it belongs to.
Can my agent list all candidates for a specific job in Greenhouse? +
Yes. Use the 'list_candidates' tool with the 'job_id' parameter. The agent will fetch all candidates associated with that specific opening flawlessly.
How do I check the current hiring stage of an applicant via chat? +
You can use the 'get_application' tool. Provide the Application ID, and the agent will return the full details, including the candidate's current stage in the hiring process natively.
Can I search for candidates who were added recently through the agent? +
Absolutely. Use the 'list_candidates' tool with sorting or filtering parameters like 'created_after'. Your agent will retrieve the most recent additions to your Greenhouse database natively.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Crisp
Chat with website visitors in real time, manage support conversations, and build a knowledge base that reduces ticket volume.
vCard Contacts Parser Alternative
Instantly convert massive iPhone and Android `.vcf` contact exports into structured JSON. Turn your AI into a hyper-intelligent local address book.
Clustdoc
Manage client onboarding and workflows via Clustdoc — track dossiers, monitor applications, and automate invitations directly from any AI agent.
You might also like
Zenloop
Analyze NPS feedback and manage customer surveys via the Zenloop API.
Sproof
Manage digital signatures, documents, and contacts on Sproof with AI agents.
GitScrum Knowledge
Build and query knowledge bases via GitScrum — manage notes as agent memory, maintain wiki pages, communicate through discussions, and search across all resources from any AI agent.