Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Local MCP gateway for approved jobs, current agent permissions and durable retry inspection.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"continuity-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp-gateway",
"--config"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add continuity-gateway -- npx -y @ramex-labs/continuity-mcp-gateway --configEste necesita valores en su línea de comandos, así que copia la configuración y complétalos.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"continuity-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp-gateway",
"--config"
]
}
}
}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ú.
Este necesita valores en su línea de comandos, así que copia la configuración y complétalos.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"continuity-gateway": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp-gateway",
"--config"
]
}
}
}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ú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
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.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub zerohourzulu, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
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.
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.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.3.0-preview.11) llegó al registro hace 28 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Thalovant MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Connect MCP clients to Thalovant control-plane and hub runtime APIs over stdio or Streamable HTTP.
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.
Message package preview — 10 October 2026: Core11, remote6, gateway11 and evidence12 add the optional saved-record explanation command. See the current release guide. Existing API/policy/proof behavior stays unchanged; older npm archives remain available.
Source preview.13: MCP client/server/core updated to 2.2.0 for GHSA-6qxp-vccf-f47h. New MCP archives are source-prepared; npm and Registry still select the earlier published tuple.
Previous source preview.12.1: Plain-language messages, completed historical ZK experiments, and retained-receipt reader source. The installable packages now include the optional saved-output explanation command; use the exact tuple in the release guide.
Current developer preview: Exact versions and installation.
Follow an investigation: Follow one protected case through interruption, replacement, a signed completion, new evidence and a persistent challenge. Run the walkthrough.
Continue an existing case: Same case, longer history, preserved permissions and unfinished duties. Start with supported profiles, migration and recovery, or the protected evidence example.
Core 0.3 preview: Build a fresh case, connect approved MCP tools, or run the public tests. The original 0.2.2 evaluation releases remain available.
[Explore the interactive demo →](https://zerohourzulu.github.io/continuity/) · Start here · Developer guide · Security and limits
[Try your own choices in the playground →](https://continuity.ramex.com/playground/) No installation or account needed.
Developer preview · Apache 2.0. Release status.
A process supervisor can start Agent B. Continuity records which role B occupies, which powers it has, what happened before, and which unfinished duties survive the change. A replacement receives its explicitly granted powers; an unfinished duty does not silently grant more authority.
The original tutorial follows a security investigation interrupted by an agent replacement. The old request is refused, the investigation stays OPEN, and the successor’s review permission is checked independently.
| You want to… | Start here | What you will learn |
|---|---|---|
| Understand the idea without installing anything | The story and answer key | Why an unfinished duty and permission are separate. |
| Run and inspect a replacement | Tutorial, then operator commands | What was refused, who holds the duty and what B may do. |
| Evaluate or integrate the code | Core 0.3 quickstart | Create your own permissions, try a protected tool, then connect a framework or policy engine. |
Use Node 22.18+ (22.x), 24.x or 26.x on macOS or Linux. Prefer the latest patch of your chosen release. No global pnpm or Python is needed for this tutorial. Full quickstart, including archive extraction.
Get the public source; no GitHub account is needed:
git clone https://github.com/zerohourzulu/continuity.git
cd continuity
<!-- /quickstart -->
See the result first, without installing dependencies:
node examples/recorded.mjs
Expect ALLOW for reviewing the investigation and DENY for collecting another packet. This inspects a bundled recorded case; it does not execute a new action.
Generate your own evidence:
node tools/setup.mjs
node tutorial/start.mjs
<!-- /quickstart -->
Expect PASS — duty remains OPEN; B has no collection power, then VERIFIED. Setup downloads locked dependencies with scripts disabled. The tutorial then runs locally using synthetic data and public test keys. It prints your new case name and exact follow-up commands. Rerunning creates another case and preserves earlier evidence.
Change one permission:
node tutorial/start.mjs --deny-review
B still inherits the duty, but its review permission becomes DENY. Expected output and explanation · Setup checks and recovery.
Keep records locally, or choose a chain-backed deployment to make selected history publicly verifiable. Cryptographic commitments can let authorized reviewers check private records without publishing their contents. This tutorial runs locally; each deployment has its own privacy, availability and finality requirements.
| Your next step | Where to go |
|---|---|
| See the idea and recorded comparison | Interactive demo |
| Inspect your new run and optional recorded Linux evidence | Operator guide |
| Integrate an authority check | Developer guide · Executable reader example |
| Try optional native enforcement mechanics | Disposable Linux lab |
| Review source provenance and validation | Validation · Presentation checks · Provenance |
| Extend the presentation | Website maintenance |
Presentation maintainers can find the separate owner-private edition in website maintenance. The public walkthrough needs no account.
Read the short development history from Core 0.1 to the current reference implementation. Contributions and public RFCs are welcome; an RFC is useful for changes to protocol behavior or security boundaries.
Core 0.2.2 is local reference software. It is not a hostile-agent sandbox, production credential system or autonomous cyber defender. The website selects recorded results; the downloaded tutorial executes Core. Real integrations must mediate every consequential operation through a protected executor. Security boundaries.
The source, tutorial, tests, reader and website are included here and in the complete evaluation download. Earlier editions remain available as historical releases; use evaluation.6 for the commands above. Package overview · Presentation provenance.
Release status and licensing · Apache 2.0 license · Third-party notices
Try the standalone developer package: install the supplied JavaScript SDK tarball in a separate application, create one authorized synthetic packet, and inspect why refused requests create none. Includes TypeScript declarations and an offline consumer check. This is an evaluation interface around unchanged Core0.2.2.
The shared-package preview connects the cooperating remote tools and MCP evidence tool to one Core dependency. Try native LangChain tools and lost-reply recovery, or the MCP evidence tool.