Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Who is wired for this role, in four plain facets, and what one change would widen it.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.korture.com/api/mcp在终端中运行这条命令
claude mcp add --transport http hiring https://mcp.korture.com/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"hiring": {
"url": "https://mcp.korture.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"hiring": {
"type": "http",
"url": "https://mcp.korture.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.korture.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 korture.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(2.0.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Starreel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Korture Hiring is a remote MCP server for hiring managers. Tell it what you want the person to get done, what the team is like, and how the place runs. It reads the role back to you and answers the question you actually have: who is likely to be wired for this, and are there enough of them.
It reads a role through four plain facets:
Each facet says where the role sits and where people suited to this kind of work usually sit, on one scale drawn from a real population. Where the role asks for more than those people normally bring, that is the rare part, and it is the reason a search stalls.
Then it counts. About 1 in how many people are wired for this role, measured against real people rather than against other job titles. If that number is small, it shows you what each make-or-break part is costing you: take this one off and about 1 in 7 becomes about 1 in 5. The preview is honest, so it will also tell you when a change makes the role narrower, or changes nothing.
When the role is already reachable, it moves you on: mint the scan link for candidates, and pull the structured interview for the role.
Free to use with a Korture account. Sign in at korture.com.
Endpoint: https://mcp.korture.com/api/mcp
| Tool | Purpose |
|---|---|
read_the_role | Is what you have said enough to read the role from, what is missing, and what to go and ask. Call it before create_brief. |
create_brief | Read the role into the nine behavioural demands: how critical each is, which are make or break, the wording each came from, and a "Will they ___?" question per hard part. |
get_brief | The finished brief. Also the tool you poll while one is generating. |
read_the_people | The four facets, about 1 in how many people are wired for the role, and what each make-or-break part would do to that if it came off. |
get_playbook | The structured interview for the role: competencies from this job, questions, and what a strong, mixed or weak answer sounds like. |
start_scan | The link a candidate opens to do their scan. |
get_scan_result | The read on one candidate. |
A credit covers one of three things: a new role, a change to a role, or a candidate finishing a scan. Your first role is free. Reading anything, a brief, a role read, an interview or a candidate, is always free.
Running out of credits stops you adding a role. It never stops a candidate mid-scan and never puts a result behind a paywall.
The band on a candidate says how congruent that person is with this role. It is not a grade on the person and not a ranking against other candidates. Different never means worse. The tools return the read in words for that reason, and an assistant reading them out should not turn them into a score.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "korture-hiring": { "url": "https://mcp.korture.com/api/mcp" } } }
Quit Claude Desktop fully and reopen. The connector appears in your tray.
The connector requires a Korture account. After you add it, Claude Desktop shows a Connect button on its connectors page. Click it. You will be sent to hire.korture.com to authenticate via email OTP, no password. Authentication takes about 20 seconds.
Once you finish, return to Claude Desktop. All seven tools become available. Your account is remembered until you revoke it from the connectors page.
Every brief-shaped response carries a links block:
links.overview: the brief on korture.comlinks.role_shape: the four facets, and where a change to the role is actually appliedlinks.candidates: candidates and their resultslinks.playbook: the structured interviewThe assistant will surface these at the end of a response. read_the_people tells you what a change would do; applying it is a decision, so it happens on the role shape page rather than in a chat.
If you previously connected to https://korture-mcp-server.vercel.app/api/mcp, update the URL above and re-authenticate. The old URL still serves traffic via a redirect, but the canonical address from now on is mcp.korture.com.
Click the button above in a browser that has Cursor installed. Cursor opens with the server name and URL pre-filled, you confirm and save.
Any MCP client that takes a remote Streamable HTTP server URL works with the same address: https://mcp.korture.com/api/mcp.
The server implements the 2026-07-28 protocol and serves 2025-era clients from the same endpoint, so it works whichever revision your client speaks.
The server participates in OAuth 2.1 with PKCE (RFC 6749 + 7636, per the MCP spec). It advertises:
https://mcp.korture.com/.well-known/oauth-protected-resource: resource metadata (RFC 9728)https://hire.korture.com/.well-known/oauth-authorization-server: authorization server metadata (RFC 8414)https://hire.korture.com/api/oauth/register (RFC 7591)MCP clients that implement DCR register themselves automatically. For service-to-service callers, an internal-tier API key is available on request.
Rate limits are tier-based. Internal and admin tiers are unlimited; the free tier is 10 briefs per day. The MCP server does not accept unauthenticated calls.
api/mcp.ts, a thin stateless gateway to hire.korture.com/api/v1/*@modelcontextprotocol/server v2 (the 2026-07-28 specification)The MCP server holds no scoring logic, no prompts, and no demand definitions. Every tool forwards to the same REST API the product itself uses, so the answers here and the answers on screen cannot drift apart. That also makes this repo safe to fork or audit publicly.
Issues and PRs welcome. For security disclosures, email team@korture.com rather than opening a public issue.