Greenhouse MCP for AI Agents. Manage candidates, applications, and jobs via chat.
Greenhouse MCP connects your AI agent directly to your recruiting pipeline. List candidates, track applications, audit job roles, and manage department data using natural conversation instead of dashboards. It gives you full visibility into hiring status without clicking through menus.
Give Claude and any AI agent real-world access
Retrieve full profile details for specific candidates or list all active users in your system.
Monitor job applications and see their current status across any active hiring process.
List and inspect all current job configurations, including department mapping and the exact stages of the hiring funnel.
Retrieve details about your company's office locations and internal departments to ensure data accuracy.
Ask an AI about this
Waiting for input…
What AI agents can do with Greenhouse: 12 Tools for Talent Acquisition
These tools let you manage every facet of your recruiting workflow—from creating new candidate profiles to auditing job stages—all through simple chat commands.
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 MCPCreate Candidate
Creates a new candidate profile record within Greenhouse.
Get Application
Retrieves specific details for any job application ID you provide.
Get Candidate
Fetches all profile information for a given candidate ID.
Get Job
Gets detailed information about a specific job posting.
Get User
Retrieves the full profile and details for an existing Greenhouse user.
List Applications
Pulls a list of all job applications that have been submitted to your company.
List Candidates
Provides an overview and listing of every candidate in your system.
List Departments
Lists all current departments recognized within the company structure.
List Job Stages
Shows you all the defined stages (like Phone Screen or Interview) for a specific job...
List Jobs
Lists every active and archived job posting in your Greenhouse account.
List Offices
Provides a list of all company office locations you manage.
List Users
Lists every user account in your Greenhouse workspace for auditing purposes.
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 each 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,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Hidden Cost of Dashboard Navigation Solved with Vinkius AI Gateway
Today, tracking talent movement means clicking through multiple tabs: you jump from the main job board to review stages, then drill down into a specific candidate's profile. You might have to open three different panels just to compare department structure against active user roles. It’s repetitive and easy to miss critical data points.
With this MCP, it changes completely. Instead of navigating, you talk. Ask your agent about the job stages for 'Product Designer,' and it pulls that specific list instantly. The entire process shrinks from five clicks across three screens down to one simple conversation.
Get Candidate Data with Greenhouse MCP
You used to have to copy a job ID, navigate the applications list, and then open the specific application record just to see who applied. This process wasted time every single day.
Now, you ask your agent. It uses `list_applications` and `get_application` together, pulling the necessary details into one readable response right in the chat window. That's how fast it is now.
What your AI can actually do with this
Managing a talent pipeline means juggling dozens of screens: the candidate list, the active jobs board, the team structure map. This MCP lets your agent access all that information inside Greenhouse—all from a simple chat prompt. You don't need to remember which dashboard holds user roles or how to find an application status; you just ask.
Need to know who applied for 'Product Designer'? Ask it. Want to see if the HR team has updated their office list? Just ask. The agent pulls that data and presents it conversationally. Because this connection is managed through Vinkius, your agent can talk to Greenhouse alongside thousands of other services you use.
You handle complex recruiting tasks using plain language chat, getting instant answers about everything from candidate profiles to departmental setup.
019d75ab-477f-7282-94e7-2b5decf6001f Here's how it actually works
The bottom line is, instead of navigating through multiple dashboards, your AI agent does all the clicking for you.
Subscribe to this MCP on Vinkius, then provide your Greenhouse Harvest API Key (v1/v2) in the connection settings.
Use your AI client's chat interface and ask a question about candidates or jobs. The agent translates that request into structured data calls.
The system fetches the relevant information from Greenhouse and presents it back to you as natural, conversational text.
Who is this actually for?
Recruiters who are tired of jumping between candidate lists and job boards. Hiring Managers who need quick status checks without leaving their desk. HR Operations staff needing to audit user permissions or department structures instantly.
You use the MCP to quickly search for candidates by name, check if they've applied, and even create a new profile when you find a promising source.
You ask the agent what stages a specific job is in or pull up a candidate’s full history to prepare for an interview without logging into the main dashboard.
You use it to verify user roles across the company or list all departments and office structures, ensuring your records match corporate policy.
What Changes When You Connect
Stop switching tabs to check status. Instead of navigating the application dashboard to see a candidate's progress, simply ask your agent for their current stage or retrieval details using get_application.
Audit your whole team instantly. Don't manually click through user lists; use the list_users tool to verify roles and access levels across departments in seconds.
Keep recruiters fast. Instead of manual searches, ask the agent to list all candidates or get details for a specific candidate using get_candidate, saving critical minutes on every search.
Understand your funnel structure. Before posting a role, use list_job_stages to see exactly what hiring steps are required for that job, ensuring nothing is missed.
See the big picture of your organization. Use the list_departments and list_offices tools to instantly map out where roles sit within your company structure when onboarding new jobs.
See it in action
The Candidate Status Check
A hiring manager needs to know if a promising candidate has progressed. Instead of logging into the application dashboard and searching by name, they ask their agent. The agent uses get_candidate to pull up the profile and instantly tells them which stage that person is in for the Senior Engineer role.
The Department Structure Audit
HR Operations needs to know if a new job falls under an existing department. They ask their agent, who uses list_departments and get_job to confirm both the organizational unit name and its proper mapping within Greenhouse.
Building a New Job Role
A recruiter is launching a new role and needs to know the standard process. They ask their agent, who runs list_job_stages, providing a clear list of mandatory steps (like Portfolio Review or Phone Screen) that must be included.
Onboarding New Users
An HR admin needs to verify user access for a newly joined department head. They use the agent, which runs list_users and get_user, to confirm current roles and necessary permissions without needing elevated dashboard rights.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Searching by keywords
Trying to find a candidate's data just because you remember they worked at 'Acme Corp'. You end up clicking through search filters and dates on the main dashboard.
Just ask your agent. Use get_candidate or list_candidates with natural language, and it handles the filtering for you.
Copying data manually
Getting a job ID from one screen and then having to paste that exact ID into another form to see the application details.
Ask your agent. It uses tools like get_job or list_applications to pull all related data in one conversational response.
Confusing roles and users
Assuming that because a department exists, every person in it is an active user with access permissions.
Separate the calls. Use list_departments to see the structure, then use list_users to audit who actually has system access.
When It Fits, When It Doesn't
Use this MCP if your core pain point is navigating and gathering complex data points from Greenhouse's specialized modules—candidate records, job stages, or organizational structures. It excels when you need the AI agent to cross-reference information (e.g., 'Show me all candidates in Marketing who applied for Job X'). Don't use this if your goal is simple document storage; don't try to manage unstructured data like legal contracts—for that, a dedicated file management tool will do better. If you only need basic CRM functionality without the deep pipeline integration of Greenhouse, a general-purpose contact database might suffice. But when the source of truth is Greenhouse, this is your fastest route.
Questions you might have
Can I use Greenhouse MCP to create a new candidate profile? +
Yes, you can. The agent has the create_candidate tool, letting you easily populate a brand-new profile record inside your system.
How does Greenhouse MCP handle department structures? +
You use the tools like list_departments and list_offices. This lets you audit the company's full structure, making sure all hiring records match up with your official organizational map.
Does Greenhouse MCP track job status? +
Absolutely. You can use tools like list_jobs and get_job to see every active posting, along with the defined steps for that role using list_job_stages.
What if I need to check a user's access level? +
You can use the specialized tools like list_users and get_user. These allow you to verify specific roles and permissions within your Greenhouse workspace quickly.
Is Greenhouse MCP compatible with all AI clients? +
Yes, this MCP is designed to work with any client that supports the Model Context Protocol (MCP), including Claude, Cursor, Windsurf, and VS Code.