Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
One-click editor setup isnβt available for this listing yet β we donβt have a confirmed install command, and weβd rather show nothing than point your editor at the wrong package or host. Follow the projectβs own setup instructions, linked above.
Yardstick is an applicant tracking system. Its hosted MCP server
(https://api.yardstick.team/mcp) gives an AI assistant 176 tools for jobs, candidates,
applications, interviews, and scorecards β so you can ask an assistant to move a
candidate forward, draft outreach, or pull a hiring report, in whatever app you
already work in.
The server is hosted: nothing to install, nothing to run, and no API key to paste into a configuration file. Point your client at the URL and sign in through your browser. It works in Claude, ChatGPT, and Claude Code; Cursor connects through a local server instead, described at https://portal.yardstick.team/docs/mcp/developer-tools along with the Yardstick CLI.
https://api.yardstick.team/mcpteam.yardstick/yardstickClaude Code
Then run /mcp and finish the browser sign-in.
Claude, ChatGPT, Perplexity, and other chat apps
Add a custom connector in the app's settings and paste in the URL above. The app reads the server and lists the tools it found.
Editors that use an mcp.json file
Step-by-step instructions for each app, including the ones that need a different shape, are at https://portal.yardstick.team/docs/mcp/chat-apps and https://portal.yardstick.team/docs/mcp/developer-tools.
Browsing the tool list needs no account: a client can connect and see what is available before anyone signs in. Everything that touches hiring data requires a signed-in Yardstick user, and the assistant can only reach what that person is allowed to reach.
Sign-in is OAuth 2.1 with PKCE, in your browser β there is no credential to copy anywhere.
Yardstick identifies a connecting app through a Client ID Metadata Document rather than OAuth Dynamic Client Registration. Apps that support the metadata-document flow find this on their own, and sign-in needs nothing from you. An app that can only register dynamically stops with an error naming dynamic client registration; that is not a misconfiguration on your side β use the Yardstick CLI or a local MCP server with that app instead.
The server reads and writes your organization's own Yardstick data, acting for whoever is signed in and limited to what that person can already reach in the app. Connecting an assistant does not widen anyone's access.
What leaves Yardstick is whatever the assistant asks for, and it goes to the assistant you connected β so that app's own terms govern what happens to it afterward. A Yardstick administrator can revoke a connection at any time from your account settings, which cuts off its access immediately.
Yardstick's own handling of your data is unchanged by this connection and is covered by the documents below.
A tool marked read-only will not change anything. The rest are not marked that way: most of them write, and a few only report status but carry no read-only guarantee. Expect your assistant to say what it is about to do before it calls one.
| Tool | What it does | Read-only |
|---|---|---|
yardstick_identity | Return the current Yardstick API principal context. | Yes |
yardstick_tasks_list | List Yardstick tasks visible to the current principal. | Yes |
yardstick_tasks_deep_link | Create a public task deep link for a caller-supplied task id. | No |
yardstick_people_list | List people visible to the current principal. | Yes |
yardstick_people_read | Read one person by public id. | Yes |
yardstick_people_create | Create a person through the public Yardstick API. | No |
yardstick_people_update | Update one person with schema-bound public API fields. | No |
yardstick_prospects_list | List active Talent CRM prospects visible to the current principal. | Yes |
yardstick_prospects_read | Read one Talent CRM prospect by public id. | Yes |
yardstick_prospects_create | Create Talent CRM prospect relationship state for an existing person. | No |
yardstick_prospects_convert_preview | Preview conversion of one Prospect into one canonical Application; bind fields are rejected and no outreach/import/merge occurs. | No |
yardstick_prospects_convert_bind | Bind an approved prospect conversion preview with explicit approval metadata and matching idempotency key. | No |
yardstick_prospects_outreach_preview | Preview a one-off prospect outreach draft without creating a draft, sending email, enrolling a sequence, or creating an application. | Yes |
yardstick_prospects_outreach_create_draft | Create a pending review prospect outreach email draft. Sending stays on email draft send and requires communications:send. | No |
yardstick_prospect_imports_dry_run | Preview a structured-row Prospect CRM import. JSON rows only; no raw CSV/resume file reads, outreach, application conversion, source ranking, or silent person merge. | No |
yardstick_prospect_imports_read | Read one Prospect CRM import dry-run/apply batch by public id. | Yes |
yardstick_prospect_imports_apply | Apply an approved Prospect CRM import preview with preview_hash and explicit row decisions for advisory matches. | No |
yardstick_ats_imports_dry_run | Preview a structured-row ATS import of candidates, jobs, and applications (source_kind: csv). JSON rows only; no raw CSV/archive file reads, no application conversion side effects, and low-confidence stage/fuzzy matches require explicit apply decisions. | No |
yardstick_ats_imports_read | Read one ATS import dry-run/apply batch and its rows by public id. | Yes |
yardstick_ats_imports_apply | Apply an approved ATS import preview with a preview_hash matching the stored dry-run. Creates people/jobs/interview_plans(stub)/job_postings/applications with idempotent replay; never sends outreach, merges people, or deletes records. | No |
yardstick_source_links_list | List source/referral attribution links without raw token material or source quality ranking. | Yes |
yardstick_source_links_read | Read one source/referral attribution link by public id without raw token material. | Yes |
yardstick_source_links_create | Create an opaque source/referral link for a published job posting. Raw source_token is returned only in the create response; reads return token_hint, and active token-bearing links also return public_url. | No |
yardstick_source_links_disable | Disable a source/referral link so its public URL no longer stamps attribution. | No |
yardstick_prospects_update | Update bounded Talent CRM prospect relationship fields. | No |
yardstick_prospect_activities_list | List bounded activity records for one Talent CRM prospect. | Yes |
yardstick_prospect_activities_create | Create a bounded internal prospect activity note or touchpoint. | No |
yardstick_talent_pools_list | List Talent CRM pools visible to the current principal. Archived pools are excluded unless include_archived is true. | Yes |
yardstick_talent_pools_read | Read one Talent CRM pool by public id. | Yes |
yardstick_talent_pools_create | Create a Talent CRM pool. | No |
yardstick_talent_pools_update | Update bounded Talent CRM pool fields. | No |
yardstick_talent_pool_members_list | List active prospect memberships for one Talent CRM pool. | Yes |
yardstick_talent_pool_members_add | Add an existing prospect to a Talent CRM pool. | No |
yardstick_talent_pool_members_remove | Remove an active prospect membership from a Talent CRM pool. | No |
yardstick_applications_list | List application person + Job attachments visible to the current principal. | Yes |
yardstick_applications_read | Read one application person + Job attachment by public id. | Yes |
yardstick_applications_create | Create a recruiter or agent-sourced application for an existing person and job posting. | No |
yardstick_applications_update | Update one application with schema-bound public API fields. | No |
yardstick_applications_transition_direct | Directly write a non-terminal application transition; approval-only statuses are rejected. Optionally target a configured stage by id with pipeline_stage_id (the resolved stage is reported back). | No |
yardstick_applications_transition_preview | Preview approval-required application transitions only; bind fields and direct-write targets are rejected. Optionally target a configured stage by id with pipeline_stage_id (status must match the stage's mapped status). | No |
yardstick_applications_transition_bind | Bind an already-previewed application transition with explicit approval metadata and matching idempotency key. | No |
yardstick_applications_archive_preview | Preview application archive approval requirements only; bind fields are rejected. | No |
yardstick_applications_archive_bind | Bind an already-previewed application archive with explicit approval metadata and matching idempotency key. | No |
yardstick_applications_status_email_poc_preview | Preview the fixed applications-owned Interviewing to Offer status/email approval POC without mutating status or email state. | No |
yardstick_applications_status_email_poc_bind | Bind the fixed applications-owned status/email approval POC with explicit approval metadata and a matching idempotency key. | No |
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/yardstick-ats-2)<a href="https://allmcps.com/mcp/yardstick-ats-2"><img src="https://allmcps.com/api/badge/yardstick-ats-2?style=directory" alt="Yardstick ATS on AllMCPs" /></a>