Spec Driven Development
作者：formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
在你的电脑上运行★ 440MIT14个月前更新
安装
Cahut
概览
作者提供的说明（英文原文）
Your AI publishes documents, decks and dashboards to your own server, and you share them by link.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 其他
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：1 项中通过 1 项
- 在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
- 注册中心没有列出需要填写的密钥。
你需要
- 在云端运行无需安装任何东西，通过互联网连接
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude：
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址，然后点击 Add
- 如果要求登录，请登录作者的服务
https://{domain}/mcp地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。
在终端中运行这条命令
claude mcp add --transport http cahut 'https://{domain}/mcp'地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"cahut": {
"url": "https://{domain}/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cahut": {
"type": "http",
"url": "https://{domain}/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
ChatGPT 只能连接互联网上的服务器：
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
- 粘贴下面的地址，起个名字，然后保存
- 如果要求登录，请登录作者的服务
https://{domain}/mcp地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。
菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上，无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
这个地址需要填入你自己的值，所以我们无法替你读取工具列表。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 cahut.cloud 验证（注册中心会核实域名所有权）
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
这个地址需要填入你自己的账户信息，所以我们无法替你检查
- – 不适用
使用 OAuth 登录
这个地址需要填入你自己的账户信息，所以我们无法替你检查
- … 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表
与“其他”中的其他服务器比较i
- 星标数多于此分类中其他 32606 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 32606 个服务器的 88% 更新
- 基础检查结果等于或优于此分类中其他 32606 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
Cahut 安全吗？
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（1.1.1）于4天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。
有什么可以替代它？
同一分类中有：Spec Driven Development, Remote Desktop Commander, Georgia MCP
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：★ 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前天更新
安装
Georgia MCP
作者：abgeo
An MCP server for Georgian public data, read from the organizations that publish it.
电脑或云端今天更新
安装
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A home to publish and share what your AIs make.
Documents, slide decks, dashboards and small apps, as pages at your address
on your own server, where your team works on them, whichever AI made them.
[Website](https://cahut.cloud) · [Documentation](https://docs.cahut.cloud) · [Brand](https://cahut.cloud/brand) · [Contributing](CONTRIBUTING.md) · [Security](SECURITY.md)
Cahut installs with one command on a Linux server. Claude, ChatGPT, Mistral Vibe or any MCP client publish to it, and you share a link instead of sending a file. Your team reads it and asks the AI for the next version, in Rooms where people and their AIs work on the same Windows. The AI does on its own what can be undone, a human approves the rest, and every action is logged.
Try it
- See what AIs published, without an account. demo.cahut.cloud/examples holds Windows that AIs made and published, each with the prompt that made it: a small shop, a deck the team comments on, a CV, a team report, a travel journal.
- Without a server, in two minutes. Sign up for My Cahut, a free Cahut at
my.cahut.cloudwith limited seats, and connect Claude or Mistral Vibe, even on their free plans, or ChatGPT on a Business, Enterprise or Edu plan. All about My Cahut. - On your own server, in one command. On a fresh Ubuntu or AlmaLinux server, with ports 80 and 443 open and a domain that points to it:
curl -fsSL https://cahut.cloud/install.sh | sudo sh -s -- --domain cahut.example.comInstallation says what the script does and how to connect your AI.
If Cahut is useful to you, a star helps others find it.
[!WARNING]
Cahut is young: its first release came out on 21 October 2026. It does not run the code of a Window on the server, take comments, export to PDF or PowerPoint, sign people in through single sign-on, or make backups. Keep snapshots of your server.
Why Cahut
Today, what your AIs make stays at the AI's place. A Claude link, a ChatGPT link, a Gamma deck: each lives on the service of the AI that made it. To publish it, share it or work on it with others, you turn it back into a file.
Word, PowerPoint and Excel were designed for humans who write, lay out and calculate by hand. When an AI makes the content, a page at its own address does better: it updates, keeps its previous version, opens to the people you choose, and keeps what its readers write.
Publish, share, work together: today, all three are hard.
- Scattered: a Claude link here, a ChatGPT link there, a Gamma deck somewhere else. Each AI keeps what it makes on its own service, so nothing is published in one place.
- Converted back: to share it, the result is turned back into a PowerPoint or a Word file, then attached and forwarded.
- Uncontrolled: who has access, until when, which version is the right one, where the data lives. Nobody really knows.
- Alone: each person works with their own AI. The team has no common place where its work lives and where it works on it together.
- Unguarded: handing a server to an AI means giving it a root shell, or going through a platform built for humans that it can barely use.
Your AIs make it and publish it. You share it and work on it together. Everything they produce lives in one place, as pages at your address, on your server, whatever the AI.
Cahut does not create content, it hosts it. It does not compete with AIs or creation tools: it is the neutral, self-hosted home where their work lives, and where your team works on it.
| Layer | Who handles it | What it brings |
|---|---|---|
| Create | The AIs (Claude, ChatGPT, Mistral...) | The content: documents, decks, dashboards, apps |
| Publish, share, work together | Cahut, on your server | A page at your address, a link opened to the right people, Rooms where the team and its AIs work, versions, search, the data of each page, Logbook |
How it works
The AIs stay outside. They connect to Cahut over MCP, drop their work through bounded operations, then disconnect. No AI model runs on the server.
flowchart LRsubgraph AI["Create: the AIs"] C[Claude] G[ChatGPT] M[Mistral Vibe] P[Any MCP client] end subgraph CAHUT["Cahut, on your server"] H["Your Cahut: publish, share, access, versions, search, data, Logbook, irreversible actions approved by you"] end subgraph READ["Read"] E[Your team] CL[Your clients] PU[The public] end AI -- MCP --> CAHUT CAHUT -- a link --> READ
- Connect. Add Cahut to your AI (MCP connector and skill) and authorize it once with OAuth, with the scope you choose.
- Create. Ask your AI for a document, a deck, a dashboard or an app, in the style you want. The skill for Claude gives it the formats.
- Publish. The AI publishes a Window to a Room, declares what it does, and gets its address back, such as
cahut.example.com/marketing/q3-review. The previous version is kept. - Share. You, or the AI within the limits you set, choose who opens each Window: its Room only, everyone in your Cahut, anyone with its Key, or the public. Anything irreversible waits for approval in the console.
- Live. Readers open the page in a browser, and a poll or a form keeps what they write in the database of its Window. The AI updates it on request. Everything goes to the Logbook.
Features
Everything below works in the latest release.
| Area | What it does |
|---|---|
| Installation | One command on a fresh VPS or dedicated server (AlmaLinux or Ubuntu), a guided first start in the browser, and cahut doctor to check the server |
| AI access | A native MCP server over HTTP, with OAuth or a personal token, for claude.ai, Claude Desktop, Claude Code, ChatGPT, Mistral Vibe and any MCP client |
| Skill for Claude | A skill that teaches Claude to make Windows and publish them, packaged as a plugin for Claude Code |
| Pages | Documents, decks, dashboards and static sites, each at its own address in its Room, in a sandbox that holds it to what its AI declares it loads and calls |
| Sharing | Window by Window: its Room only, internal (everyone in the Cahut), a Key (a password) or public, with an optional end date; share links that open a Window without an account, until they end |
| Invitations | A Window sent by e-mail, to people of the Cahut or outside it, with a personal link in place of its Key |
| Versions | Two versions kept per Window, a rollback in one gesture, and a trash |
| Search | Find any page, deck or dashboard of your Rooms by a word of it or a tag |
| Data | A SQLite database for each Window, on your server: polls, forms, petitions and trackers keep what their readers write |
| Users and Rooms | The people of each Cahut and its admins, a personal Room for each person, team Rooms with owners and members |
| Sign-in | Accounts of each Cahut, with a link by e-mail for a forgotten password |
| Knock first | What an AI cannot undo waits for its person, who approves or declines it in the console |
| Web console | In English and French: Knocks, Rooms, Windows, people, connected AIs and the Logbook under /console/ of each Cahut, and a console for the administrators of the server under /server/ |
| Domains and TLS | Several Cahuts per server, each at its own domain or subdomain, no wildcard needed, automatic certificates |
| Limits | People, Rooms, Windows and disk for each Cahut, set by the administrators of the server, and Cahuts where each person works alone |
| Moderation | Reports of Windows from anyone, without an account; the administrators of the Cahut and of its server withdraw a Window with a reason, and reinstate it |
| Logbook | History of every action: who, which AI, on whose behalf, with what result |
| Updates | Daily, from the signed releases on GitHub, with a snapshot of the databases and a rollback |
What Cahut does not do:
- Create content: that is the AIs' job.
- Run an AI model on the server: the AIs stay outside and connect to it.
- Depend on one AI vendor, or lock work into a proprietary format.
- Give an AI free access to the server.
- Run across several machines: one server holds one or more Cahuts.
Governance: knock first
The AI is the intended operator of Cahut, but never without guardrails.
- Bounded operations. The AI acts through typed operations over MCP (publish a Window, change its data, make a share link), never through a free shell.
- Reversible or approved. What can be undone, the AI does alone. What cannot waits for a human to approve it in the console, with a notification and an expiry.
- The AI declares what it publishes. Each version of a Window states whether its pages run scripts, the origins they load from and call, where their forms send, and the data they keep.
- Per-agent permissions. Each AI acts on behalf of a person, with the Rooms and the scope that person grants, revocable at any time.
- Everything is logged. Which AI, on whose behalf, which action, which result: the Logbook is readable in the console.
- Data stays home. Windows, their data and the Logbook live on your server.
- Isolation. Each Window runs in a sandbox: its scripts cannot read the other Windows, the console or the reader's session. The SQL of its data runs in a worker process of its own, confined by Landlock on Linux. The Cahuts of one server share nothing but the machine.
| The AI does it alone (reversible) | A human approves (irreversible) |
|---|---|
| Publish or update a Window (the previous version is kept) | Purge a Window from the trash, or delete a team Room |
| Open a Window to its Room, its Cahut or a Key, until a date | Make a Window public |
| Put a Window in the trash, and restore it | Add a person to a Cahut, or delete one |
| Roll back to the previous version | Change the role of a person, the members of a Room or their roles, or widen the reach of an AI |
| Change the data of a Window, after a copy it goes back to | Remove a table or a column from the data of a Window |
FAQ
Why not share a Claude artifact or a ChatGPT link?
Each lives on the service of the AI that made it, and is shared on that service's terms. Cahut keeps the work of every AI in one place, on your server, at your address. Each Window opens to the people you choose, keeps its previo
只显示了开头部分；其余内容请在仓库中阅读