Spec Driven Development
de formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar
Cahut
Resumen
Descripción del creador (original en inglés)
Your AI publishes documents, decks and dashboards to your own server, and you share them by link.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en la nube
- Transporte: Streamable HTTP
- Categoría: Otros
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
- El registro no indica ninguna clave que completar.
Necesitas
- Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
- Abre Settings → Connectors
- Presiona Add custom connector
- Pega la dirección de abajo y presiona Add
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://{domain}/mcpLa dirección tiene partes {…} que solo tú conoces (como tu cuenta), así que cópiala y complétalas.
Ejecuta esto en tu terminal
claude mcp add --transport http cahut 'https://{domain}/mcp'La dirección tiene partes {…} que solo tú conoces (como tu cuenta), así que cópiala y complétalas.
O copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"cahut": {
"url": "https://{domain}/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
La dirección tiene partes {…} que solo tú conoces (como tu cuenta), así que cópiala y complétalas.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"cahut": {
"type": "http",
"url": "https://{domain}/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
- Abre ChatGPT en la web → Settings → Connectors (Apps)
- Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
- Pega la dirección de abajo, ponle un nombre y guarda
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://{domain}/mcpLa dirección tiene partes {…} que solo tú conoces (como tu cuenta), así que cópiala y complétalas.
Los nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
La dirección necesita tus propios valores, así que no podemos leer la lista de herramientas por ti.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio cahut.cloud (el registro comprueba quién es dueño del dominio)
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
La dirección necesita datos de tu propia cuenta, así que no podemos revisarla por ti
- – No aplica
Inicio de sesión con OAuth
La dirección necesita datos de tu propia cuenta, así que no podemos revisarla por ti
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con otros en Otrosi
- Más estrellas que el 0% de los otros 32537 servidores de esta categoría
- Publicado en el registro más recientemente que el 89% de los otros 32537 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 32537 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Cahut?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (1.1.1) llegó al registro hace 4 días.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
¿Qué puedo usar en su lugar?
En la misma categoría: Spec Driven Development, Remote Desktop Commander, TF Rooms
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Remote Desktop Commander
de desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Se ejecuta en la nube★ 211Actualizado ayer
Instalar
TF Rooms
de tfrooms.com
Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.
Se ejecuta en la nubeActualizado hoy
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo