Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Yardstick ATS
Overview
Description from the maker (original English)
Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.yardstick.team/mcpRun this in your terminal
claude mcp add --transport http yardstick https://api.yardstick.team/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"yardstick": {
"url": "https://api.yardstick.team/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"yardstick": {
"type": "http",
"url": "https://api.yardstick.team/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.yardstick.team/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain yardstick.team (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32606 servers in this category
- Published to the registry more recently than 74% of the other 32606 servers in this category
- Basic checks equal to or better than 100% of the other 32606 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Yardstick ATS safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.6.14) reached the registry 12 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Georgia MCP
by abgeo
An MCP server for Georgian public data, read from the organizations that publish it.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
Only the beginning is shown; read the rest in the repo