mcp-greenhouse
Integrates with Greenhouse Harvest API to manage candidates, jobs, applications, and candidate profiles. Provides tools for searching candidates, retrieving full candidate profiles, listing jobs, viewing job details, and browsing applications.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-greenhouseFind candidates for the Senior Developer role"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-greenhouse
Greenhouse MCP Pack — wraps the Greenhouse Harvest API v1
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| Search candidates in your ATS. Returns names, IDs, email addresses, and application status. Use greenhouse_get_candidate for full profile details. |
| Get full candidate profile by ID. Returns resume, contact info, application history, interviews, and notes. |
| Browse open and closed job postings. Returns titles, IDs, departments, statuses, and posting dates. Use greenhouse_get_job for full details and candidate pipeline. |
| Get complete job details by ID. Returns description, requirements, hiring team, and linked applications. |
| View job applications across your pipeline. Returns applicant names, job IDs, application status, and submission dates. Filter by job or stage (e.g., 'screening', 'interview'). |
Related MCP server: jd-intel-mcp
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"greenhouse": {
"url": "https://gateway.pipeworx.io/greenhouse/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/greenhouse/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Greenhouse data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
AI resume triage for recruiters. Query your candidate pool from Claude or ChatGPT.
Query professional profiles, search candidates, and get AI-powered summaries and job fit analysis.
Manage job applications — jobs, companies, boards, notes, and profile — from your AI client.
Search companies, enrich contacts, and reveal emails and phones from your AI agent.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with the PeopleBox Applicant Tracking System (ATS) to manage candidates, positions, and recruitment pipelines. It provides tools for searching candidate profiles, adding notes, and tracking application timelines through natural language interfaces.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to fetch and structure job postings from major ATS platforms (Greenhouse, Lever, Ashby, etc.) directly, eliminating copy-paste and context loss.392MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pull live job listings from major ATS platforms (Greenhouse, Lever, Ashby, Workable), Hacker News hiring threads, and detect hiring signals on company career pages.-
- AlicenseAqualityDmaintenanceEnables integration with Ashby ATS to search candidates, view applications, submit interview feedback, and manage recruiting workflows through natural language.916MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-greenhouse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server