Hiring Mender Mcp

io.github.headlessherm-creatorPublished by GitHub account headlessherm-creatorv0.1.0Updated Oct 29, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant create candidates, move applications between stages, and reject applicants in BambooHR and Greenhouse through one…

What you can do
  • Create candidates and applications in BambooHR or Greenhouse with platform-specific fields
  • Advance or move an application to a new stage or status, with a stale-move guard on Greenhouse
  • Reject an application (Greenhouse only; BambooHR uses a rejection status via advance)
  • List valid BambooHR applicant status IDs, or Greenhouse candidates as a substitute for stage IDs
  • List candidates and applications, optionally filtered by job ID
When to use it
Useful when an AI recruiting workflow needs to write to an applicant tracking system and you want one tool vocabulary instead of separate BambooHR OAuth and Greenhouse Harvest integrations. Best for teams already running one or both of those ATS platforms.
Requirements
Node.js v18 or later and a local install of the npm package. Credentials via environment variables: BAMBOOHR_COMPANY_DOMAIN and BAMBOOHR_ACCESS_TOKEN (OAuth 2.0 token with hiring:applications.write scope) and/or GREENHOUSE_HARVEST_API_TOKEN; only the variables for the platform you use are needed. Network access to the ATS APIs.
Before you install
The server makes real write calls to your ATS: it creates candidates, moves applications and rejects applicants, which changes hiring records. It sends data to BambooHR and Greenhouse using the credentials you supply. Greenhouse Harvest keys are all-or-nothing within the endpoints you enable, so create a narrow key; request only the hiring:applications.write BambooHR scope rather than broad HR access.

Installation

In SourceWeft

  1. Open Hiring Mender Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit c16d086

Tools

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.

Parametersplatformrequiredcandidaterequired

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.

ParameterstoJobIdplatformrequiredstatusIdtoStageIdfromStageIdapplicationIdrequired

reject_application

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

ParametersplatformrequiredapplicationIdrequiredrejectionNotesrejectionReasonId

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.

ParametersjobIdplatformrequired

list_candidates

List candidates/applications, optionally filtered by job ID.

ParametersjobIdplatformrequired

Version history

1
  1. v0.1.0LatestOct 22, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts