Hiring Mender Mcp

io.github.headlessherm-creator由 GitHub 帳號 headlessherm-creator 發布v0.1.0更新於 Oct 29, 2026

Local MCP server: BambooHR + Greenhouse ATS write tools, one vocabulary.

已驗證STDIO僅桌面效率與工作流商業與電商

概覽

AI 產生的概覽

本機 MCP 伺服器,讓助理用一套統一工具在 BambooHR 與 Greenhouse 建立候選人、推進申請階段並拒絕申請。

可以做什麼
  • 在 BambooHR 或 Greenhouse 建立候選人與申請,欄位依平台而異
  • 將申請推進或移動到新的階段或狀態,Greenhouse 端具備防止過期移動的檢查
  • 拒絕申請(僅 Greenhouse;BambooHR 以帶拒絕狀態的推進操作達成)
  • 列出 BambooHR 有效的申請人狀態 ID,或改為列出 Greenhouse 候選人
  • 列出候選人與申請,可依職缺 ID 篩選
適用情境
適合需要讓 AI 招募流程寫入申請人追蹤系統,又不想分別維護 BambooHR OAuth 與 Greenhouse Harvest 兩套整合的情況。最適合已在使用這兩個 ATS 平台之一的團隊。
執行需求
需要 Node.js v18 以上版本,並在本機安裝該 npm 套件。憑證透過環境變數提供:BAMBOOHR_COMPANY_DOMAIN 與 BAMBOOHR_ACCESS_TOKEN(具 hiring:applications.write 權限的 OAuth 2.0 權杖)和/或 GREENHOUSE_HARVEST_API_TOKEN;只需設定所用平台的變數。需要能連線至 ATS 介面的網路。
安裝前請注意
此伺服器會對 ATS 發出實際寫入:建立候選人、移動申請與拒絕申請,都會變更招募紀錄。它會用你提供的憑證把資料傳送給 BambooHR 與 Greenhouse。Greenhouse Harvest 金鑰在所啟用的端點範圍內是全有全無,應建立範圍最小的金鑰;BambooHR 只申請 hiring:applications.write 權限,不要授予更廣的人事資料存取。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Hiring Mender Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Hiring Mender MCP — BambooHR & Greenhouse ATS Write Tools for AI Agents

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.

The problem this solves

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.

Tools

  • create_candidate — create a new candidate/application. BambooHR: firstName, lastName, jobId, etc. Greenhouse: first_name, last_name, job_id, etc.
  • advance_application — move a candidate to a new stage/status. BambooHR uses a numeric status ID (list_statuses first). Greenhouse uses from_stage_id (required, guards against stale moves) and to_stage_id/to_job_id.
  • reject_application — reject a candidate (Greenhouse only; BambooHR rejections go through advance_application with a rejection status ID).
  • list_statuses — list valid BambooHR applicant status IDs, or Greenhouse candidates for a job.
  • list_candidates — list candidates/applications, optionally filtered by job ID.

Setup

1. Install Node.js (v18+): https://nodejs.org

2. Clone and install:

bash
git clone https://github.com/headlessherm-creator/hiring-mender-mcp.gitcd hiring-mender-mcpnpm install

3. Get API credentials:

  • BambooHR: Requires an OAuth 2.0 access token with the hiring:applications.write scope. See BambooHR's OAuth docs.
  • Greenhouse: Requires a Harvest API key, created by a user with "Can manage ALL organization's API Credentials" permission, via Configure → Dev Center → API Credential Management. See Greenhouse's Harvest API docs.

4. Set environment variables:

bash
export BAMBOOHR_COMPANY_DOMAIN=yourcompanyexport BAMBOOHR_ACCESS_TOKEN=your_oauth_tokenexport GREENHOUSE_HARVEST_API_TOKEN=your_harvest_token

You only need to set the variables for the platform(s) you're using.

5. Point your MCP client at it:

json
{  "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"      }    }  }}

Setup docs for common clients:

Security note

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.

Keywords

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.

Related tools

Same local-first philosophy, different problems:

License

MIT

來源:README.md,提交 c16d086

工具

5

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必填

advance_application

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_application

Reject a candidate's application. Greenhouse only (BambooHR uses advance_application with a rejection status ID instead).

輸入參數platform必填applicationId必填rejectionNotesrejectionReasonId

list_statuses

List 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

List candidates/applications, optionally filtered by job ID.

輸入參數jobIdplatform必填

版本歷史

1
  1. v0.1.0最新Oct 22, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分