Greenhouse MCP

io.github.benmonopoliPublished by GitHub account benmonopoliv0.3.2Updated Oct 24, 2026

Production-ready MCP server for Greenhouse with 175 tools for recruiting teams

VerifiedSTDIODesktop onlyBusiness & Commerce

Server details

Identifier: io.github.benmonopoli/greenhouse-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account benmonopoli for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.benmonopoli%2Fgreenhouse-mcp.svg)](https://sourceweft.com/mcp/io.github.benmonopoli%2Fgreenhouse-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives an assistant 175 tools for working with Greenhouse recruiting data.

What you can do: Greenhouse MCP is a production-ready MCP server for Greenhouse, described as providing 175 tools aimed at recruiting teams. It runs as a local process over stdio, so the assistant starts it on the user's machine rather than connecting to a hosted endpoint. The registry description does not enumerate the individual tools, so the exact operations available are not documented here.
When to use it: Consider it when an assistant needs to work with Greenhouse recruiting data and the user wants that access through a locally run MCP server. It is aimed at recruiting teams and recruiting workflows.
Requirements: Runs as a local process over stdio, installed from the PyPI package open-greenhouse-mcp, so a Python environment is needed. The manifest declares no authentication, environment variables, or headers, and no remote endpoint. Desktop only; not available as a web executable.

Before you install

The manifest declares no authentication and no environment variables or headers, but the server is described as production-ready for recruiting data, which is typically sensitive personal and candidate information. The registry description does not list the tools, so what the server can read or change in Greenhouse cannot be verified from the supplied material. Review the tool list and permissions before pointing it at a live Greenhouse account.

Installation

In SourceWeft

Open Greenhouse MCP in the dashboard and add it to a workspace.
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.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.2LatestSep 16, 2026

Score

25% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
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 listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.