Greenhouse MCP for AI. Manage candidate pipelines from your chat.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Greenhouse lets your AI agent manage every step of your hiring pipeline from a single chat window. You can list and get details on applications, track candidate activity feeds, and even submit job posts or new candidates—all without leaving your workflow.
It's the full control panel for recruiters who hate switching tabs.
What AI agents can do with Greenhouse Automation
List board departments
Lists every department that has published jobs and what those departments are called.
List board jobs
Retrieves a list of all currently active job posts across the entire board.
List board offices
Lists every physical office location and what jobs are associated with it.
The MCP can list every published job post across various departments or offices.
It retrieves the complete, chronological activity feed for any specific candidate ID.
The MCP allows you to pull details on existing applications or delete outdated entries from candidate profiles.
It can submit an application directly to a specific job board using required credentials.
You can add applications to existing candidate profiles or submit entirely new prospects and candidates into the system.
Ask an AI about this
Waiting for input…
What AI agents can do with Greenhouse Alternative: 16 Tools
Use these tools to perform specific actions—like listing jobs or updating records—by calling them through your AI agent's natural language interface.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Greenhouse on VinkiusList Board Departments
Lists every department that has published jobs and what those departments are called.
List Board Jobs
Retrieves a list of all currently active job posts across the entire board.
List Board Offices
Lists every physical office location and what jobs are associated with it.
List Partner Jobs
Shows a list of job openings that are visible to external partner users.
Submit Board Application
Submits a candidate's application directly through the job board API key credentials.
Submit Partner Candidate
Sends new candidates or prospects into the Greenhouse system for tracking.
Update Application
Modifies specific details on an existing application record, like changing a status or adding notes.
Add Application To Candidate
Attaches a new application record to an existing candidate profile.
Create Partner Tracking Link
Generates a unique link for job sourcing that tracks the source of the lead.
Delete Application
Removes a specific candidate application record from the system.
Get Application
Retrieves all details for one single, specified job application.
Get Audit Log Events
Pulls a list of recent system and user activity log events.
Get Board Job
Fetches the full details, including questions, for one specific job post.
Get Candidate Activity Feed
Retrieves a complete timeline of all recorded actions and status changes for a...
Get Partner Candidates
Gets the current status of candidates who came through partner channels.
List Applications
Provides a list containing basic information for all active applications in...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
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
Built on the Model Context Protocol (MCP) for 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 connection provides 16 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The daily struggle of switching between recruiting dashboards and ATS forms.
Right now, checking a single candidate's file requires a painful dance: you open Greenhouse, click 'Activity Feed,' check status X; then you have to switch tabs to the Job Board to see if it’s still listed; after that, you jump back to update their record, making sure you don't miss any details.
With this MCP connection, your agent handles all those clicks. You just ask for a candidate's status or history, and the information is compiled instantly into your conversation. It takes the whole messy process and boils it down to one direct answer.
Get complete control over job listings using Greenhouse.
You used to have to run separate queries just to list departments, then check which jobs were open in each department's specific board. It was a multi-step process that often missed outdated postings or incomplete data points.
Now, you can ask the agent to `list_board_jobs`, and it pulls every active job post across all boards into one clean list. You get comprehensive visibility without ever leaving your chat window.
What your AI can actually do with this
Managing talent acquisition used to mean logging into dozens of different dashboards just to check a status update. Now, you can talk to your AI client and get everything done in one conversation. This MCP connects directly to Greenhouse so your agent handles candidate record maintenance, job posting visibility, and application tracking automatically.
Need to know what happened with Candidate X? Your agent pulls the complete activity feed instantly. Need to update a status or add new information to an old profile? Just ask. Whether you're working in VS Code, Cursor, or Claude, your agent uses Vinkius to handle all the messy backend work.
It keeps your data clean and up-to-date, letting you focus on interviewing people instead of managing databases.
019e5d22-4074-7157-bbbc-7584f325a233 Here's how it actually works
The bottom line is that you never have to manually log into the Greenhouse website again; your AI client handles it all.
First, subscribe to this MCP and provide your Greenhouse API Token.
Next, call any function through your AI client (like Claude or Cursor) telling it exactly what you need done—e.g., 'List all applications for the Engineering department.'
Finally, the agent executes the request against Greenhouse and returns structured data directly to your chat window.
Who is this actually for?
Recruiters and Sourcers who are tired of jumping between ATS, email clients, and job board sites. This is for HR Operations staff who need to maintain clean candidate records without spending their day copying data.
Checking a candidate's status or running a list of all open roles across different departments.
Reviewing application details for top candidates right when they sit down to work, without needing HR support.
Automating the maintenance of candidate records, such as adding a new job board post or updating an old applicant's file.
What Changes When You Connect
You stop toggling tabs. Instead of opening a separate dashboard just to see if Jane Doe moved status, you ask for the get_candidate_activity_feed and get the whole story in one response.
Running a report on all applicants is instant. Use list_applications to pull bulk data or use list_board_jobs to check what's open without manually visiting every department page.
When you find a great candidate from a partner source, you don't need manual entry. You just call submit_partner_candidate, and the record is clean and ready to go.
Need to update something? Instead of finding the right form, you use update_application directly through your agent conversation, changing statuses or adding notes instantly.
You can even create specialized links for sourcing by calling create_partner_tracking_link. This ensures every lead is tracked back to its source.
See it in action
Quickly verifying a candidate's status
A recruiter needs to know if Candidate Smith has completed all interviews. They ask their agent to run get_candidate_activity_feed for Smith. The agent immediately returns the latest steps, showing the technical interview was finished yesterday and an offer is pending.
Posting jobs across multiple departments
A hiring manager needs a list of all open roles to review with their team. They ask the agent to run list_board_jobs, which quickly compiles all active posts from every department, saving them from navigating separate departmental pages.
Handling new external leads
A sourcing specialist gets a promising lead through a partner network. They tell their agent to run submit_partner_candidate, and the MCP handles the data formatting and submission, keeping Greenhouse updated instantly.
Cleaning up old application records
An HR ops specialist finds an application that is totally irrelevant or outdated. Instead of manually deleting it in the backend, they ask the agent to use delete_application on the specific record ID for clean data maintenance.
The honest tradeoffs
Treating Greenhouse like a spreadsheet
Trying to manually update 20 applications by logging in and changing status fields one by one. This is slow, error-prone, and takes hours.
Let your agent run update_application for all 20 records in a single prompt. The MCP handles the bulk updates instantly, preserving data integrity across the board.
Losing track of candidate sources
Sourcing new candidates without generating specific tracking links, so you can't prove where they came from later.
Always call create_partner_tracking_link first. This generates a unique source-tracked link that ensures every lead is properly attributed in the system.
Asking for job details without context
Just asking 'What about jobs?' which gives you nothing useful and forces you to guess what board or department they mean.
Be specific. Tell your agent to run get_board_job and reference the exact Job ID, ensuring you pull back the precise details and questions associated with that single opening.
When It Fits, When It Doesn't
Use this MCP if your core workflow involves reading, modifying, or submitting records within Greenhouse. Specifically, if you need to check a candidate's full history using get_candidate_activity_feed, list all open jobs via list_board_jobs, or submit new data through the partner channels. Don't use this MCP if your only goal is reporting on historical trends over years—you might be better off with a dedicated BI tool that connects to an export endpoint. If you just need to view what departments exist, running list_board_departments gives you basic structure; but if you want actionable data (like current status updates), this MCP is the right call.
Questions you might have
How do I use the add_application_to_candidate tool in Greenhouse? +
You tell your agent that you want to attach a new application and provide the necessary IDs. The MCP handles sending the data through the API, ensuring the record links correctly to the existing candidate.
Does list_board_jobs show all current job openings on Greenhouse? +
Yes, it lists every active job post across your entire board. This is useful because you can get a full overview without checking department by department.
How do I check the history of a candidate using get_candidate_activity_feed? +
Simply ask the agent to retrieve the activity feed for that specific candidate ID. It returns a detailed, chronological list of every status change and interaction recorded.
Can I submit job applications with the MCP? (submit_board_application) +
Yes, you can use submit_board_application if your agent has the required Job Board API Key credential. You just need to provide the target board and application details.
How do I use the list_applications tool to view my candidate pipeline? +
The list_applications tool retrieves a full summary of all applications in your Greenhouse account. You can get key details like the job title, status, and associated candidate name for quick overviews.
What information does the get_audit_log_events tool provide? +
This tool pulls detailed audit log events for your organization's Greenhouse usage. It helps you track who made changes to records and when those actions occurred, improving accountability.
How do I update existing candidate data using the update_application tool? +
You use the update_application tool by providing the necessary application ID and the specific fields you want to change. This allows targeted modifications without affecting other records.
What is needed to run the get_partner_candidates function? +
The get_partner_candidates tool requires authentication via your Partner API credentials. Once connected, it retrieves candidate status directly through the designated Partner API endpoints.
Can I see the history of interactions with a specific candidate? +
Yes, you can use the get_candidate_activity_feed tool with a candidate's ID to retrieve their full activity history, including notes and status changes.
How do I list all open positions on our job board? +
Use the list_board_jobs tool providing your job board token. This will return all active job posts currently published.
Is it possible to update application details directly through the AI? +
Yes, the update_application tool allows you to modify existing application fields by providing the application ID and the data payload.
We've already built the connector for Greenhouse. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 16 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.