Back to Browse

Hiring Mender MCP Server

Developer ToolsModerate5.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.8
Moderate5.8Moderate Risk

This is a legitimate BambooHR and Greenhouse applicant-tracking integration. Credentials are read from environment variables, there are no hardcoded secrets, and network calls go only to the vendors' own APIs, which matches its stated purpose. The main concerns are low-severity input-handling issues: unencoded IDs interpolated into URLs and query strings, and unfiltered spreading of caller-supplied fields into request bodies. Write and destructive tools such as reject_application have no confirmation step. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

4 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

BAMBOOHR_COMPANY_DOMAINRequired
BAMBOOHR_ACCESS_TOKENRequired
GREENHOUSE_HARVEST_API_TOKENRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "hiring-mender-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hiring-mender-mcp@0.1.0"
      ],
      "env": {
        "BAMBOOHR_ACCESS_TOKEN": "your-bamboohr-access-token-here",
        "BAMBOOHR_COMPANY_DOMAIN": "your-bamboohr-company-domain-here",
        "GREENHOUSE_HARVEST_API_TOKEN": "your-greenhouse-harvest-api-token-here"
      }
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub 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:

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:

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

Reviews

No reviews yet

Be the first to review this server!