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
Cahut
Overview
Description from the maker (original English)
Your AI publishes documents, decks and dashboards to your own server, and you share them by link.
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://{domain}/mcpThe address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Run this in your terminal
claude mcp add --transport http cahut 'https://{domain}/mcp'The address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cahut": {
"url": "https://{domain}/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.
The address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"cahut": {
"type": "http",
"url": "https://{domain}/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://{domain}/mcpThe address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Menu 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
The address needs your own values, so we cannot read the tool list for you.
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 cahut.cloud (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 applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
- – Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
- … 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 32583 servers in this category
- Published to the registry more recently than 88% of the other 32583 servers in this category
- Basic checks equal to or better than 100% of the other 32583 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 Cahut 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 (1.1.1) reached the registry 4 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, sync. labs
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 yesterday
Install
sync. labs
by synchronicity-labs
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
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.
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
Only the beginning is shown; read the rest in the repo