Spec Driven Development
作者：formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
在你的电脑上运行★ 440MIT14个月前更新
安装
Yardstick ATS
概览
作者提供的说明（英文原文）
Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 其他
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：1 项中通过 1 项
- 在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
- 注册中心没有列出需要填写的密钥。
你需要
- 在云端运行无需安装任何东西，通过互联网连接
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude：
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址，然后点击 Add
- 如果要求登录，请登录作者的服务
https://api.yardstick.team/mcp在终端中运行这条命令
claude mcp add --transport http yardstick https://api.yardstick.team/mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"yardstick": {
"url": "https://api.yardstick.team/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"yardstick": {
"type": "http",
"url": "https://api.yardstick.team/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
ChatGPT 只能连接互联网上的服务器：
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
- 粘贴下面的地址，起个名字，然后保存
- 如果要求登录，请登录作者的服务
https://api.yardstick.team/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上，无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 yardstick.team 验证（注册中心会核实域名所有权）
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
- … 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
- … 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表
与“其他”中的其他服务器比较i
- 星标数多于此分类中其他 32589 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 32589 个服务器的 74% 更新
- 基础检查结果等于或优于此分类中其他 32589 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
Yardstick ATS 安全吗？
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（0.6.14）于12天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。
有什么可以替代它？
同一分类中有：Spec Driven Development, Remote Desktop Commander, Detailing Manager
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Remote Desktop Commander
作者：desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
在云端运行★ 211昨天更新
安装
Detailing Manager
作者：RadoslavMoshev
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
在你的电脑上运行今天更新
安装
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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/mcpThen 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.
| 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 |
yardstick_decision_brief_read | Read the decision brief for an application. | Yes |
yardstick_decision_brief_regenerate | Regenerate a decision brief for an application with idempotency metadata. | No |
yardstick_applications_email_decision_preview | Preview the candidate email decision for an application status change without mutating the application or drafts. | No |
yardstick_applications_email_decision_apply | Apply an application status-change email decision with idempotency metadata. | No |
yardstick_email_drafts_list | List candidate email drafts with optional status and email-type filters. | Yes |
yardstick_email_drafts_read | Read a redacted candidate email draft. | Yes |
yardstick_email_drafts_preview | Read rendered preview content for a candidate email draft. | Yes |
yardstick_email_drafts_history | Read candidate email draft history and provenance. | Yes |
yardstick_email_drafts_update | Save mutable candidate email draft fields or set/clear a validated sender override. | No |
yardstick_email_drafts_send | Send a pending candidate email draft with replay protection, or reclaim a never-delivered draft and send it. | No |
yardstick_email_drafts_discard | Discard a pending candidate email draft without provider mutation. | No |
yardstick_email_automation_settings_read | Read candidate email automation settings. | Yes |
yardstick_email_automation_settings_update | Update candidate email automation settings. | No |
yardstick_email_sender_settings_read | Read redacted email sender settings with sanitized queue diagnostics. | Yes |
yardstick_email_sender_connections_list | List redacted sender provider connection state. | Yes |
| yardstick_email_templates_list | List
只显示了开头部分；其余内容请在仓库中阅读