Greenhouse MCP Goes Open Beta July 6. The ATS Just Became Optional.
Greenhouse MCP hits open beta July 6, 2026. What Workday's June launch, a 412% application flood, and three week-one workflows mean for TA.
On July 6, 2026, Greenhouse flips its Model Context Protocol server from Design Partner beta to Open Beta for every Site Admin on the new Core, Plus, and Pro tiers. Four weeks earlier at DevCon, Workday shipped its own MCP-native Agent-Ready Tools with Claude, ChatGPT, Gemini, and Copilot support. Two ATS incumbents, one protocol, and a very short window before the workflows built on top of them stop being a competitive edge and start being table stakes.
What actually ships on July 6
Greenhouse first announced its MCP server on May 7, 2026, and spent June inside a design-partner cohort that included StubHub and Komodo Health. July 6 opens that same server to every Site Admin on Core/Plus/Pro. The v1 tool set is deliberately read-heavy: curated MCP tools, org-level controls, permission-aware access, rate and safety limits, and self-service docs. Write actions exist (Formation Bio's team is already doing bulk edits via Claude Code) but the shape of the release is governed read access first, agentic writes second.
The connective tissue matters more than any single tool. Greenhouse's June 10 launch bundled six AI features across role setup, interview note-taking, candidate insights, and analytics. MCP is not one of the six. It is the plane the other five (and every third-party agent your team is already sneaking in) plug into.
Meredith Johnson, Greenhouse's CPO, and Robby Perdue, VP of Product Management, have been careful in the on-record positioning: this is "governed connectivity, not an open pipe." That phrasing is the whole product. Access follows existing Greenhouse permissions. Every agent action is auditable. IT and security get a sanctioned path instead of the shadow integrations your TA ops lead has been quietly wiring up since Q1.
Workday made MCP the default in 30 days
At Workday DevCon on June 2, 2026, Jay Wieczorkowski (GM, Developer Platform) unveiled Developer Agent, Agent-Ready Tools, and Agent Passport. The Agent-Ready Tools "provide controlled guardrails for agents to access HR and finance data over Model Context Protocol." Developer Agent plugs into Claude Code, Cline, Codex, Cursor, and Google Antigravity. Agents that call Workday through the native tools "automatically inherit Workday's security and delegation model, business process controls, and audit trail."
Read that last clause twice. It is the reason the third-party wrapper ecosystem (Zapier's Greenhouse MCP, CData's read-only Workday and Greenhouse MCP servers, Merge's Agent Handler with DLP for SSNs and passport numbers, Composio's Tool Router) is about to get repriced. Wrappers translate REST or SOAP into MCP. Native servers inherit the vendor's permission and audit model by default. Enterprise procurement will pay for the second thing and reluctantly tolerate the first.
Two ATS incumbents, both shipping native MCP inside 60 days of each other, is how a protocol becomes a category standard. If you are a TA leader still deciding whether to have an opinion on this, the decision has been made for you.
The 412% is the real story
Greenhouse's June 10 announcement buried the number that actually forces adoption: applications are up 412% since 2023 while open roles have stayed roughly flat. Recruiter headcount dropped 56% between 2022 and 2025. Seventy-four percent of candidates say they use AI in their job search, and 30% of the 2,950 job seekers Greenhouse surveyed are already using AI agents to search, submit, and schedule.
CEO Daniel Chait calls the current dynamic a "doom loop": AI floods the top of the funnel with noise, which makes it harder for real candidates to reach real jobs, which makes recruiters lean harder on AI to triage, which invites more noise. LinkedIn is now processing 11,000 job applications per minute, up 45% year over year. Chait is not wrong.
Framing MCP as an "AI feature" undersells what Greenhouse is actually shipping. This is a capacity release with a compliance wrapper. The ATS vendor is admitting the arms race cannot be won with headcount and handing customers the escape hatch. That is why the July 6 date matters and why "wait and see" is not a strategy that ends well.
MCP does not make the ATS more powerful. It makes it optional.
For 20 years the ATS was the center of gravity in recruiting. Every workflow started in Greenhouse or Workday, ran through a stage change or a scorecard, and ended in an offer letter template. In 2026 that inverts. The agent handles the workflow. The ATS becomes a database and a compliance system, not an active recruiting tool.
Greenhouse and Workday both know this. It is why they are racing to be the governed system-of-record data plane rather than the UI you spend your day inside. Whoever owns the audited data pipe wins even if a recruiter never logs into the product again.
MCP is a shadow-IT amnesty program dressed up as an AI feature.