Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
One board for every AI you use: agents claim tasks and finish with proof you accept or return.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://letsweft.com/api/mcp在终端中运行这条命令
claude mcp add --transport http weft https://letsweft.com/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"weft": {
"url": "https://letsweft.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"weft": {
"type": "http",
"url": "https://letsweft.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://letsweft.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
发布者(letsweft.com)不是仓库所有者(AndreiFinogeev);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.2)于13天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AI Deprecations
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One board for every AI you use: agents claim tasks and finish with proof you accept or return.
Weft is a task board for solo founders and small teams who work with AI. One hosted MCP server means VS Code, Claude, ChatGPT, Cursor, Copilot CLI, JetBrains, Kiro, Codex, Gemini CLI, Warp, goose, Raycast, Perplexity, Grok, Le Chat and a dozen more all work from the same board — no extra plugins needed. Thirty-three of them have a copy-paste setup guide.
What makes it a board for agents rather than a to-do list with an API: an agent claims a task with a lease, reports progress to keep it, and finishes with a receipt — artifacts you can check, and what it did not do — which you accept or send back from an Inbox, on the web or your phone. When it needs a decision only you can make, the question waits for you instead of being guessed at.
| Endpoint | https://letsweft.com/api/mcp |
| Transport | Streamable HTTP — MCP 2026-07-28, and 2025 revisions for older clients |
| Auth | OAuth 2.1 — Authorization Code + PKCE, dynamic client registration (RFC 7591): a browser window opens to sign in with your Weft account on first use. For clients without OAuth (scripts, CI, some CLIs), a personal access token from Settings → Access tokens, sent as Authorization: Bearer wft_… — see access tokens. |
| Manifest | /.well-known/mcp.json |
| Registry | Published in the official MCP Registry as com.letsweft/weft (domain-verified namespace) |
A free account takes a minute: letsweft.com/sign-up — the free plan includes 50 active tasks and 200 tool calls a month.
Setting this up from inside an agent (Cline, Cursor, a CLI)? Point it at llms-install.md — the same steps, written for a machine.
VS Code — install the Weft extension (also on Open VSX, which is where Cursor, Windsurf and VSCodium look) and the server registers itself. Without an extension, add to .vscode/mcp.json, or run "MCP: Open User Configuration" to have it in every workspace:
{ "servers": { "weft": { "type": "http", "url": "https://letsweft.com/api/mcp" } } }
Switch Chat to Agent mode and ask for your board; VS Code opens a browser for OAuth the first time.
GitHub Copilot CLI — run copilot, type /mcp add, choose HTTP, paste the endpoint, leave headers empty, set tools to *.
Claude Code
claude mcp add --transport http weft https://letsweft.com/api/mcp
Cursor — Add to Cursor, or add to ~/.cursor/mcp.json:
{ "mcpServers": { "weft": { "url": "https://letsweft.com/api/mcp" } } }
Replit — Add to Replit, or Integrations → "MCP Servers for Replit Agent" → "Add MCP server".
ChatGPT — published plugin: Plugins → search "Weft" → Connect.
Codex CLI
codex mcp add weft --url https://letsweft.com/api/mcp
Gemini CLI — official extension:
gemini extensions install https://github.com/AndreiFinogeev/weft-gemini-extension
JetBrains (via Junie) / Kiro / Warp / goose / Raycast / Perplexity / Grok / Le Chat / Claude Desktop / Lovable / Windsurf / Cline / Zed / anything else — add https://letsweft.com/api/mcp as a remote MCP server (custom connector) and complete OAuth. Per-client walkthroughs: letsweft.com/integrations.
| Category | Tools |
|---|---|
| Search | search, fetch |
| Board | initialize_board, get_board_state, list_columns |
| Tasks | list_tasks, create_task, bulk_create_tasks, update_task, move_task, trash_task, restore_task, archive_done_tasks |
| Doing the work | get_my_work, start_task, report_progress, complete_task |
| Asking the human | request_input, submit_answer |
| Memory of decisions | record_decision, get_context, get_task_history |
| Projects | list_projects, create_project, update_project |
| Sprints | list_sprints, get_active_sprint, create_sprint, start_sprint, complete_sprint, add_task_to_sprint, remove_task_from_sprint |
The four in Doing the work are the ones that make this a board for agents rather than a to-do list with an API. start_task CLAIMS a task with a lease and returns a runId and leaseToken; report_progress renews the claim, because an agent that dies mid-run cannot report anything and silence is the only signal the board has. complete_task takes a structured receipt — artifacts a person can check, claims, what was explicitly NOT done — and when the task carries machine-checkable verification, the server re-runs those checks itself before the card moves to Done.
request_input is the other half: a question only the person can answer survives the session it was asked in, waits in their Inbox (web or phone), and comes back to whichever client asked.
Destructive tools carry MCP safety annotations; deleting is safe — trash_task keeps tasks recoverable for 30 days. Full reference: letsweft.com/docs/mcp-tools.
Your board is private: every session is scoped to your account via OAuth, and tokens are issued per client. Tasks created by AI carry creator attribution, so the board always shows who (or what) added each card.