Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Greenhouse to Claude Code

Let Claude advance candidates and tag prospects in Greenhouse. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Greenhouse to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Greenhouse, you add a Greenhouse MCP server: a small hosted service that exposes Greenhouse's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Greenhouse account. No API keys pasted into config files.

claude mcp add --transport http greenhouse https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Greenhouse once connected?

Full read-write Greenhouse access lets Claude advance or reject a candidate at a stage, add a private note, tag a prospect, move a prospect into a job, and add recruiters or coordinators to a job's hiring team once you approve. The pipeline hygiene that used to mean clicking through every application happens where the role already lives.

  • Advance or reject a candidate at a specific interview stage
  • Read submitted scorecards and interview feedback for an application
  • Add a private note or tag to a candidate or prospect
  • Move a prospect into a job and assign a recruiter or coordinator
  • Schedule or update an interview against an existing stage
  • Draft a rejection or outreach email for your review before it sends

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Greenhouse access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Greenhouse API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Greenhouse changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Greenhouse connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Greenhouse connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Greenhouse account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Greenhouse's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Greenhouse?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Greenhouse account it signs in with. Revoking access is one click in Greenhouse.

More on the Greenhouse connector

Greenhouse connector for claude.aiDeel + Claude CodeJustworks + Claude CodePaychex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us