Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Individual-analyst context layer: recall, remember, and reconcile your data and engineering context.
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.
AuthorizationLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Ejecuta esto en tu terminal
claude mcp add --transport http clarilayer https://clarilayer.com/api/mcp/mcp --header 'Authorization: your-value'Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"clarilayer": {
"url": "https://clarilayer.com/api/mcp/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}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ú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"clarilayer": {
"type": "http",
"url": "https://clarilayer.com/api/mcp/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}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ú.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Authorization secreto obligatorio HTTP headerEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub clarilayer, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
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.
Debes completar: Authorization
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.
El repo de GitHub cambió por última vez –, y la última versión (0.31.0) llegó al registro hace 3 meses.
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.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, debuff
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
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.
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
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.
ClariLayer
Your AI should remember how you work.
Turn selected past conversations into memory your AI can use across projects and sessions.
Website · Docs · Connect your AI · Quickstart
ClariLayer keeps the facts, preferences, decisions, rules and lessons you choose to carry forward. Connect Claude Code, Cursor, Codex, claude.ai or another compatible remote MCP client. Your AI can recall relevant work context from the selected authorized space, with its source and applicability visible.
Start free. No credit card for the current personal offer.
You settle a launch decision with your AI:
For the Launch project, show the product demo first. Technical detail belongs in docs. Remember this confirmed decision with its source and project applicability.
In a later session:
Recall the Launch project's saved decisions before drafting the launch page. Show which decision applies and where it came from.
The decision can travel across projects and sessions within the authorized space while retaining its original applicability. A rule for one customer or project stays bounded. If it changes, correct it; if it no longer belongs, use scoped forget or exclusion.
Recall depends on the AI client actually calling the tool. Connecting MCP does not guarantee every answer uses saved context.
Use [Connect your AI](https://clarilayer.com/connect-ai) for guided setup. Select your client and space, give the setup request to that AI, and complete authentication in the client. Use OAuth when the selected route supports it, or store a context key locally as the fallback. Never paste a key into an AI conversation or a GitHub issue.
Already connected? Choose Update my AI setup on the same page, then run its request in the intended project. This updates one recognized ClariLayer instruction block while preserving your own instructions.
| Client | Project instruction target |
|---|---|
| Claude Code | CLAUDE.md |
| Codex | AGENTS.md |
| Cursor | .cursor/rules/clarilayer.mdc |
| claude.ai / other remote clients | Follow the connection and runtime guidance supported by that client |
The installed bootstrap obtains the current workflow from get_project_stanza with mode: "runtime" once at the first relevant use in each new AI session. A routine server guidance update then reaches the next session without copying another long workflow into every project.
The npm CLI supports context-key connection setup and a local dbt check. CLI 0.3.0 replaces the embedded Analytics instructions with a request for your connected AI and adds instructions --agent .
Check which version is available before choosing a command:
npm view clarilayer version
With 0.3.0 or later available:
npx clarilayer@latest init
npx clarilayer@latest instructions --agent codex
If your registry still serves 0.2.1, use npx clarilayer@0.2.1 init --no-stanza to skip its older embedded instructions, then complete Update my AI setup through the guided setup above. The hosted path is available independently of npm publication.
See CLI.md for options and the source-checkout route, CHANGELOG.md for release history, and RELEASING.md for publication checks. Native instruction qualification records the tested client and its limits.
Full setup, manual connection examples and troubleshooting: [QUICKSTART.md](./QUICKSTART.md).
| Work | How it works |
|---|---|
| Recall | recall_context retrieves relevant saved context across the selected authorized space. Preserve source and applicability; project and purpose are relevance hints, not permissions. Fetch complete entries with get_context_entry when needed. |
| Remember or correct | remember with work_context saves confirmed durable facts, preferences, decisions, rules and lessons. Ambiguous changes and suggestions remain candidates for review. |
| Forget | Recall the target first, then use its returned entry ID for the requested forget operation. Do not guess names or delete related entries without a separate request. |
| Complete the context loop | context_checkpoint records the AI's bounded completion declaration. It does not prove the AI used the right context or completed an external task. |
| Report use | report_context_use optionally links bounded feedback to delivered context. A delivery receipt alone is not evidence of answer quality. |
The hosted MCP service was checked on September 17, 2026: capability v64 · server 0.39.0 · 23 tools. Use the live capabilities tool for the current list and versions. Capability reference.
After connection, you can choose supported local history, a destination space and an extraction provider, then inspect the exact preview before accepting an initial import. Ongoing capture requires a separate setup and grant for the sources you choose. Connecting MCP alone does not read history or enable capture.
Source support and extraction-provider support are separate. The current qualified extraction path uses a version-specific Claude CLI profile; OpenAI and Cursor extraction providers are unavailable, and native Cursor history qualification is limited. Check the current history guide before choosing a source.
Selected source content is processed by the chosen extraction provider. ClariLayer stores the extracted context rather than a raw transcript archive. Provider processing may use your allowance or incur provider usage charges.
Optional semantic search has separate organization consent and provider disclosure in Settings. A new connection or history-import choice does not grant that consent. Lexical recall remains available without it.
ClariLayer for Analytics retains its specialist tools:
get_analysis_context recalls definitions, schema notes, saved queries and related context. Recall previews can be truncated; use get_context_entry for full bodies, stored SQL and CRM contracts.bootstrap imports supplied SQL, dbt models, notes, data dictionaries and semantic models. It does not read a repository or warehouse by itself.reconcile compares a saved definition with supported warehouse or bounded, row-free HubSpot evidence supplied by your agent. Salesforce contracts can be stored and recalled; Salesforce reconcile is disabled.General work and engineering context are not independently reconciled. Live trust statuses remain `asserted` / `caveat`; verified is not live.
Watch the Analytics reconcile example
A seeded Analytics demo. Your agent supplies the warehouse evidence; a mismatch becomes a caveat for later sessions. This illustrates the Analytics specialist path.
cd your-dbt-project
dbt docs generate npx clarilayer dbt-check
The CLI compares local manifest.json and catalog.json files for phantom columns, missing catalog models, type-family mismatches and empty descriptions. No account or warehouse connection is needed for the local check. With an explicit --save, bounded findings are staged as proposals in your Context Inbox for review. --save --dry-run previews the payload without a network request.
See the CLI reference and Analytics recipes. The August 2026 dbt drift survey retains its method, evidence and limitations for the published 0.2.1 check.
propose / propose_batch for review. Pending proposals are not live recall context. Ad hoc conversation harvest requires an explicit request and sends distilled candidates, not the transcript.This repository's docs, examples, recipes and setup/dbt CLI are MIT licensed. The hosted ClariLayer service is proprietary. This repository is the public starting point for connecting to the service.
The Governed Context Edge is available through a hand-run private team pilot. Request early access.
For contributions and setup help, see CONTRIBUTING.md.