Writes the job post and the interview plan, keeps the Greenhouse pipeline moving, and drafts the offer and the first week.
Built for: The hiring manager or small people team running four open roles in Greenhouse alongside a day job.
The button opens the checkout, where the 2 servers and 6 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Write a job post with an interview guide and scoring rubric, then open the job in Greenhouse.
Summarise where every candidate stands, which applications have waited too long, and what the next step is.
Prepare each interviewer's questions and scorecard, and collect the feedback into one debrief.
Draft the offer as a Word document within the band, then the onboarding plan once it is signed.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
Greenhouse Harvest: jobs, candidates, applications, notes and pipeline stages, with read-only and recruiter tool profiles.
Creates and edits Word documents — for the offer letter and the interview packet that leave the building as .docx.
Anthropic's hiring packet: job post, structured interview guide with a scoring rubric, and an offer letter template, from one brief.
Competency-based questions and scorecards for each interviewer, so four interviews do not ask the same thing.
Tracks candidates through sourcing, screens, interviews and offers, and says where the pipeline is stuck.
Benchmarks and band placement for an offer, and whether it is competitive for the role.
The offer letter with base, equity and sign-on, and negotiation notes for the hiring manager.
The pre-start checklist, the first week and 30/60/90-day goals for the new hire.
Every member is free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Open Greenhouse | Free | — |
| Office Word | Free | — |
| Skills | ||
| Job Post Builder | Free · context cost only | — |
| Interview Prep | Free · context cost only | — |
| Recruiting Pipeline | Free · context cost only | — |
| /comp-analysis | Free · context cost only | — |
| /draft-offer | Free · context cost only | — |
| /onboarding | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 2 servers and 6 skills, and all 54 tools.
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add hiring-desk writes all 2 servers into Claude Code’s config in one go — or run the lines below one by one. The 6 skills are not included — add them with lines 03–08.
# 01 · Open Greenhouse
claude mcp add --scope user open-greenhouse-mcp '--' uvx --with 'mcp<2' open-greenhouse-mcp
# 02 · Office Word
claude mcp add --scope user office-word-mcp '--' uvx --from office-word-mcp-server word_mcp_server
# 03 · Job Post Builder
npx mcprush@latest skill add anthropics/job-post-builder
# 04 · Interview Prep
npx mcprush@latest skill add anthropics/interview-prep
# 05 · Recruiting Pipeline
npx mcprush@latest skill add anthropics/recruiting-pipeline
# 06 · /comp-analysis
npx mcprush@latest skill add anthropics/comp-analysis
# 07 · /draft-offer
npx mcprush@latest skill add anthropics/draft-offer
# 08 · /onboarding
npx mcprush@latest skill add anthropics/onboardingnpx).uvx, docs.astral.sh/uv).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Office Word | imported | 35 |
| Open Greenhouse | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 1 member of 2 has no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
The maintainer lists no alternatives for this stack.
Written by the maintainer, kept on the page rather than in a support thread.
It does not make hiring decisions or rank people by protected characteristics. It organises evidence; people decide.
Candidate data is personal data. Use the read-only profile until writes are needed, and keep exports out of shared folders.
Compensation benchmarks are only as good as the data you give the skill; it has no market survey of its own.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Reads, writes and fixes Word, Excel and PDF files on your own machine, without opening Office for each one.
Tools to inspect code changes, run checks and prepare a pull request review.
Tools to investigate a bug report and work toward a reproducible test case.