Is this an official Greenhouse MCP server?

No. It is Memtro's MCP server with Memtro's Greenhouse connector behind it: the connector reads Greenhouse through its API with the credentials you connect on Dashboard → Connections, and Greenhouse publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Greenhouse?

Not yet. Today every Greenhouse tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · People and HR

Greenhouse MCP server

Greenhouse in any MCP client, through Memtro: Greenhouse does not publish this server. Memtro's Greenhouse connector reads Greenhouse through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only recruiting: open jobs with hiring teams and stages, candidates and their applications, pipeline per stage, scorecards, upcoming interviews and offer status. Never reads compensation.

Reads

greenhouse_jobsJobs (open by default) with departments, offices, hiring team and opening counts; filter by department or name.
greenhouse_candidatesFind candidates by email (exact), by name (matched over the most recently updated candidates), by job, or recently active.
greenhouse_candidateOne candidate's full picture: profile, every application with job, stage and status, submitted scorecards…
greenhouse_pipelineThe pipeline for one job: applications grouped by current stage with counts and candidate names (active applications by default).
greenhouse_interviewsScheduled interviews in a window (default today through the next 7 days) with candidate, job, interviewers and their responses.
greenhouse_offersOffers with status (unresolved, accepted, rejected, deprecated), dates and start date, with candidate and job names.

Connect it

First connect Greenhouse on Dashboard → Connections, then add Memtro to your client once. The Greenhouse tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Greenhouse connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How many candidates are in onsite for the Backend Engineer role?
› Who interviewed Ann Lee and what did they recommend?
› What interviews are scheduled this week?
› Which offers are still unresolved?

Questions

Is this an official Greenhouse MCP server?: No. It is Memtro's MCP server with Memtro's Greenhouse connector behind it: the connector reads Greenhouse through its API with the credentials you connect on Dashboard → Connections, and Greenhouse publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Greenhouse?: Not yet. Today every Greenhouse tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.