create_candidate
Create a new candidate/application in BambooHR or Greenhouse. For BambooHR, provide jobId and firstName/lastName/email/phoneNumber. For Greenhouse, provide job_id and first_name/last_name/email.
platform必填candidate必填
io.github.headlessherm-creator由 GitHub 帳號 headlessherm-creator 發布v0.1.0更新於 Oct 29, 2026
Local MCP server: BambooHR + Greenhouse ATS write tools, one vocabulary.
本機 MCP 伺服器,讓助理用一套統一工具在 BambooHR 與 Greenhouse 建立候選人、推進申請階段並拒絕申請。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
參照 儲存庫 中的啟動說明。
A free, local MCP server that creates candidates, advances/moves applications, and rejects candidates in BambooHR and Greenhouse — one consistent tool vocabulary across both platforms, so you don't hand-roll two different ATS integrations.
If you're building an AI recruiting workflow and keep rewriting the same candidate-creation/stage-advance logic for BambooHR's OAuth API and Greenhouse's Basic Auth Harvest API, this is the MCP server for that exact problem.
BambooHR's Applicant Tracking API and Greenhouse's Harvest API both support real write operations — creating candidates, moving them through pipeline stages, rejecting applications — but they use completely different auth schemes (OAuth 2.0 bearer tokens vs. HTTP Basic Auth with a blank password) and completely different field names and endpoint shapes. There is no free, open-source tool that normalizes both behind one set of calls. This is that tool.
firstName, lastName, jobId, etc. Greenhouse: first_name, last_name, job_id, etc.list_statuses first). Greenhouse uses from_stage_id (required, guards against stale moves) and to_stage_id/to_job_id.advance_application with a rejection status ID).1. Install Node.js (v18+): https://nodejs.org
2. Clone and install:
3. Get API credentials:
hiring:applications.write scope. See BambooHR's OAuth docs.4. Set environment variables:
You only need to set the variables for the platform(s) you're using.
5. Point your MCP client at it:
Setup docs for common clients:
Greenhouse Harvest API keys are all-or-nothing within the scope you grant them — the key can access every endpoint type you enable when you create it, not just the ones this tool uses. Create a Harvest key with only the endpoints this tool needs (candidates, applications) rather than reusing a broad existing key. Same caution applies to the BambooHR OAuth scope — request only hiring:applications.write, not broader HR data access.
This server makes real network calls to BambooHR's and Greenhouse's APIs using the credentials you provide — unlike a fully local tool, your data does leave your machine, going directly to the ATS vendor you're already using. No third party, telemetry, or logging is involved.
BambooHR MCP server, Greenhouse MCP server, ATS MCP server, applicant tracking system AI agent, recruiting automation MCP, HR MCP server, hiring pipeline automation, candidate management MCP, Claude MCP recruiting tools.
Same local-first philosophy, different problems:
MIT
來源:README.md,提交 c16d086
Create a new candidate/application in BambooHR or Greenhouse. For BambooHR, provide jobId and firstName/lastName/email/phoneNumber. For Greenhouse, provide job_id and first_name/last_name/email.
platform必填candidate必填Advance/move a candidate's application to a new stage/status. BambooHR: pass applicationId and statusId (use list_statuses first). Greenhouse: pass applicationId, fromStageId (required — guards against stale moves), and toStageId or toJobId.
toJobIdplatform必填statusIdtoStageIdfromStageIdapplicationId必填Reject a candidate's application. Greenhouse only (BambooHR uses advance_application with a rejection status ID instead).
platform必填applicationId必填rejectionNotesrejectionReasonIdList valid status/stage IDs for a platform. BambooHR: returns applicant statuses (needed before advance_application). Greenhouse: use the Greenhouse UI/Job API for stage IDs; this returns candidates instead as a practical substitute.
jobIdplatform必填List candidates/applications, optionally filtered by job ID.
jobIdplatform必填已滿足適用檢查項的 90%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
git clone https://github.com/headlessherm-creator/hiring-mender-mcp.gitcd hiring-mender-mcpnpm installexport BAMBOOHR_COMPANY_DOMAIN=yourcompanyexport BAMBOOHR_ACCESS_TOKEN=your_oauth_tokenexport GREENHOUSE_HARVEST_API_TOKEN=your_harvest_token{ "mcpServers": { "hiring-mender": { "command": "node", "args": ["/path/to/hiring-mender-mcp/src/index.js"], "env": { "BAMBOOHR_COMPANY_DOMAIN": "yourcompany", "BAMBOOHR_ACCESS_TOKEN": "your_oauth_token", "GREENHOUSE_HARVEST_API_TOKEN": "your_harvest_token" } } }}