.webp?dpl=dpl_ANvo1LrZK33j6BD7qnAJSFdkie6L)
An ATS your AI agent can actually operate.
Claude Code or Codex runs the yardstick command-line tool, and Claude, ChatGPT or any MCP-connected assistant uses Yardstick's hosted MCP server. Both are on every account, with a public API, so the agent you already work in can read where hiring stands and prepare the next piece of work. The decisions a candidate can see stay with you.
What the agent reads, and what it prepares.
You are already working in an agent. The question is whether your hiring system can be reached from inside it, or whether it stays a browser tab you leave the conversation to go visit.
In Yardstick it can be reached, and the model is worth being precise about. You have a real discussion with your own agent, where you bring the business context that is not written down anywhere. Your agent runs Yardstick to turn that discussion into work: an interview plan for the role as you actually described it, the questions, the scorecard, the drafts. What comes back is an artifact in Yardstick that you look at and change before it counts.
What your agent can read
Where a role stands. Jobs, job postings, hiring pipelines, and the applications sitting in each stage.
Who a candidate is and what has happened to them. The person record, the application, the job it is attached to, and the interviews scheduled against it.
What the panel is going to ask. The published interview plan, which is the questions and the written anchors for what each score means, plus the interviewers assigned to each session.
Whether the evidence is in yet. Who still owes feedback on a role, and the hiring decision brief once the assigned scorecards are complete.
Where your outreach stands. Prospects, prospect activity, talent pools, source and referral links, candidate email templates and their versions, and any candidate email drafts waiting for review.
Who changed what. API events and the audit log.
Every tool carries a human-readable title and read-only or destructive hints, so your assistant's consent screen tells you what a tool does before you approve it.
What it prepares, and what you sign off
| Your agent prepares | You approve before |
|---|---|
| Job descriptions | Publishing a job |
| Interview plans, questions and scorecards | Advancing or rejecting a candidate |
| Summaries of candidate evidence | Making or communicating a hiring recommendation |
| Scheduling and email drafts; prospect pipelines, talent pools and outreach sequences | Sending an ad-hoc candidate email outside an approved sequence |
| Candidate messages inside a sequence you have already approved | Activating an outreach sequence that sends candidate email |
| Changing permissions, API tokens or billing |
The discussion your agent turns into a plan can carry more than the role description. If you want the plan aimed at a specific gap on the team, context-aware hiring is how your team's metrics reach that same conversation. And the recurring work that runs on a schedule rather than on your ask is handled by the built-in agents, each with one job and its own destination. To decide which steps of a hire to hand to either kind, walk through what to automate in hiring.
Connecting it.
1. A coding agent. Install the
yardstickCLI and authenticate. Claude Code, Codex or a similar agent runs it for you. The CLI is agent-agnostic.2. A general assistant over MCP. Add Yardstick's hosted remote MCP server as a connector at
https://api.yardstick.team/mcpand sign in with OAuth. ChatGPT and Claude both connect this way. Setup is in the MCP documentation, and the MCP server page lists what its 176 tools cover and the connect steps for each client.3. Your own code. The public REST API is the same surface the other two run on, so a coding agent and a chat assistant share one system of record.
Access is scoped to what you can already see and tokens are short-lived. Over the MCP server, every write-capable tool requires an explicit idempotency key, so a retry cannot apply the same write twice.
All three ship on every account, including the free one. Pricing is pay-as-you-go: you pay for active hiring rather than for seats or an annual contract.
Where Yardstick fits.
Yardstick is worth a look in two cases.
You want a coding agent to run hiring, not a chat window. The yardstick CLI is a command-line tool, so Claude Code or Codex operates your hiring system the same way it operates the rest of your stack, and the public API is underneath both it and the MCP server.
You want the interview structure in the same place as the agent surface. The plan, the questions, the scorecard with its written anchors and the decision brief are the record your agent works against, so what it prepares comes back structured rather than as prose you have to file somewhere.
And it is on every account, including the free one, without a sales conversation first.
If you are moving from Greenhouse, the switch-from guide covers the import.
The MCP server, the API and the CLI are on every account.
Questions people ask.
Does Yardstick work with Claude Code?
Yes. Claude Code can operate Yardstick two ways: run the yardstick CLI, or connect to Yardstick's hosted MCP server with one command, claude mcp add --transport http yardstick https://api.yardstick.team/mcp, then finish the browser sign-in. Both are on every account, including the free one. Claude Code prepares the work, such as job descriptions, interview plans and scorecards, and email drafts. Publishing a job, advancing or rejecting a candidate, and sending a candidate email outside an approved sequence wait for your approval.
Does Yardstick have an MCP server?
Yes. It is a hosted remote MCP endpoint at https://api.yardstick.team/mcp, OAuth-protected and live on every account.
Can I connect Claude to my ATS?
In Yardstick, add the hosted MCP server at https://api.yardstick.team/mcp as a connector in Claude and sign in with OAuth. Claude then reads where hiring stands and prepares work in it, and the actions a candidate can see wait for your approval.
Can ChatGPT read my ATS?
In Yardstick, add the MCP server as a connector in ChatGPT and sign in. It reads jobs, pipelines, applications, interview plans, who still owes feedback and the decision brief, scoped to what your own account can already see.
Do I need a coding agent to use it?
No. A coding agent such as Claude Code or Codex uses the yardstick CLI, and a general assistant uses the MCP server. Both run on the same public API.
Can the agent email candidates on its own?
Candidate email sends inside a sequence you have approved, or as a single message you have approved. Nothing else.
Is any of this a paid or Enterprise feature?
No. The MCP server, the public API and the CLI are on every account, including the free one.
Put your hiring system where your agent already is.
A hosted MCP server, a public API and a yardstick CLI on every account, with the interview plans, scorecards and candidate evidence your agent works against. Your first three Jobs are free.