Yardstick ATS MCP server

<!-- Generated from the Yardstick tool catalog. Do not edit by hand; edits here are overwritten. -->

Yardstick ATS — MCP server

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.

• Server URL: https://api.yardstick.team/mcp
• Documentation: https://portal.yardstick.team/docs/mcp
• Tool reference: https://portal.yardstick.team/docs/mcp/tools
• Registry name: team.yardstick/yardstick

Add Yardstick to your assistant

Claude Code

claude mcp add --transport http yardstick https://api.yardstick.team/mcp

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

{
  "mcpServers": {
    "yardstick": {
      "url": "https://api.yardstick.team/mcp"
    }
  }
}

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.

Signing in

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.

Your data

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.

• Privacy Policy — https://www.yardstick.team/privacy-policy
• Data Processing Agreement — https://www.yardstick.team/dpa
• Terms of Service — https://www.yardstick.team/terms

What it can do

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.

Shortened. The full README is on GitHub.