Hiring Mender MCP server

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

• createcandidate — create a new candidate/application. BambooHR: firstName, lastName, jobId, etc. Greenhouse: firstname, lastname, jobid, etc.
• advanceapplication — move a candidate to a new stage/status. BambooHR uses a numeric status ID (liststatuses first). Greenhouse uses fromstageid (required, guards against stale moves) and tostageid/tojobid.
• rejectapplication — reject a candidate (Greenhouse only; BambooHR rejections go through advanceapplication with a rejection status ID).
• liststatuses** — list valid BambooHR applicant status IDs, or Greenhouse candidates for a job.
• listcandidates** — list candidates/applications, optionally filtered by job ID.

Setup

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

2. Clone and install:

git clone https://github.com/headlessherm-creator/hiring-mender-mcp.git
cd hiring-mender-mcp
npm 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:

export BAMBOOHR_COMPANY_DOMAIN=yourcompany
export BAMBOOHR_ACCESS_TOKEN=your_oauth_token
export 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:

{
  "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:

• Claude Desktop: https://modelcontextprotocol.io/quickstart/user
• Cursor: https://docs.cursor.com/context/model-context-protocol
• Claude Code: https://docs.claude.com/en/docs/claude-code/mcp

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.

Shortened. The full README is on GitHub.