Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Your own network — goals, commitments and interaction history — read-only, from your assistant.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://www.tendladder.com/api/mcp在终端中运行这条命令
claude mcp add --transport http tend https://www.tendladder.com/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tend": {
"url": "https://www.tendladder.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tend": {
"type": "http",
"url": "https://www.tendladder.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://www.tendladder.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
发布者(tendladder.com)不是仓库所有者(ruimluis);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Systemdox
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Read-only access to your own Tend record — goals, contacts, commitments and interaction history — so your assistant can answer from your network instead of guessing.
https://www.tendladder.com/api/mcp
Streamable HTTP · OAuth 2.1 · read-only · requires a Tend account (the free plan includes the connector).
This repository is the connector's documentation and its registry manifest.
The server itself is hosted — there is nothing here to install or run.
Tend is goal-coupled relationship management: your network organized around what you are trying to achieve, rather than a contact list on a reminder timer.
The connector exists because the useful question is usually asked somewhere Tend has no app — in the middle of a conversation with your assistant, on a phone, in a thread about a job you are trying to fill. It answers from your own record, and it never spends your Tend allowance: the reasoning runs on your assistant's plan, not ours.
One click: Add Tend to Claude — this opens Claude's Add connector dialog with the name and URL already filled in. Review them, confirm, then click Allow on the consent screen, which appears on tendladder.com rather than a third-party login. That is the whole setup: no token to paste, no config file to edit.
The link only prefills the form. It grants nothing until you confirm.
By hand, if you would rather: in Claude, Settings → Connectors → Add custom connector, and paste https://www.tendladder.com/api/mcp.
Claude Code: claude mcp add --transport http tend https://www.tendladder.com/api/mcp
Verified on Claude desktop, web and mobile. Other MCP clients speak the same protocol and are expected to work, but only Claude is tested — ChatGPT requires Developer mode, and Gemini currently has no consumer path for remote MCP servers.
Every connected client is listed in Tend's settings with its own Revoke.
The connector tells your assistant the questions it answers best, so asking *"what can I do with Tend?"* returns a useful list on the first try. These are the six it names:
| Ask | What it does |
|---|---|
| *What do I owe people this week?* | Your open commitments, the ones you promised |
| *What am I waiting on?* | The other direction — what others owe you |
| *Who should I contact today, and why that person?* | Ranked, with the reason attached |
| *Which of my goals is stalling?* | The goal that has stopped moving, and why |
| *Brief me on Dana before I speak to her.* | Everything on one person, in reading order |
| *Here is a job spec — who in my network is relevant?* | Paste anything; it matches against your network |
That last one is the one Tend's own app cannot do, because it cannot see what is in front of you and your assistant can.
Seven, all read-only.
| Tool | Returns |
|---|---|
list_goals | Your goals and their state |
get_goal_next_moves | The next moves on a goal, with the audit's own reasoning and its age |
list_commitments | Open commitments, each carrying a direction — mine or theirs |
search_contacts | Contacts matching a query, ranked |
get_contact | One person in full |
search_activities | Interaction history |
list_reminders | What is scheduled |
Rows carry deep links back into Tend, so anything your assistant creates elsewhere stays traceable to why it mattered.
Read-only is a hard boundary, not a first version's limitation. No tool creates, edits, sends or deletes. The worst outcome of a confused agent is a wrong answer, never a changed record — which is the property that made shipping this early defensible in the first place.
Published to the Official MCP Registry as com.tendladder/tend. The manifest is server.json.
Questions, or something behaving oddly: open an issue here, or use the contact route at https://www.tendladder.com/.
The documentation and manifest in this repository are MIT licensed (see LICENSE). The Tend service itself is proprietary and is not distributed here.