Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Flashcards, quizzes, and cloze cards with spaced repetition, as an inline MCP App.
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": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add memora -- npx -y @servation/memora-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-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ú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"memora": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@servation/memora-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ú.
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 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub Servation, 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.1.1) llegó al registro hace 4 meses.
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, FactLot
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.
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
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.
Turn any conversation into an interactive study session, right inside Claude Desktop. Ask Claude to make a deck and it generates the cards, then renders them as an inline review you can click through: flip flashcards, answer multiple-choice quizzes, and fill in cloze blanks. Every answer updates a spaced-repetition schedule, and your results flow back to Claude so it can drill what you missed.
Keywords: Model Context Protocol, MCP server, MCP Apps, Claude Desktop, flashcards, quizzes, spaced repetition, SRS, FSRS, Anki alternative.
Built on the MCP Apps extension (SEP-1865): core MCP spec 2025-11-25 plus the Apps extension 2026-01-26.
Three ways to study, all rendered inline and all graded the same way:
[...] in a card front and it becomes a cloze card automatically.Spaced repetition: every grade updates a per-card FSRS schedule (via ts-fsrs), so weak cards resurface sooner and due cards come first. Ask *"what's due today?"* for a summary across all your decks.
Organize with categories: name decks with :: to nest them (e.g. LLM::Attention). Browse the category tree, or the same tree as an interactive mind map, and study a whole branch in one merged session. Quiz decks are flagged with a badge.
Manage your decks: create, append to, edit, rename, and delete decks and cards without leaving the chat. Pass reverse when creating a deck to also drill each card back-to-front (handy for vocabulary).
Just JSON: decks live in data/decks.json, read live on every call. Hand-edit them or let Claude build them. No database, no external service.
Only review_deck and study open the inline flip-card UI; everything else returns a text summary, so editing or creating in chat no longer pops the widget.
| Tool | What it does |
|---|---|
review_deck | Open one deck for review (due cards first, capped per session). |
study | Review a whole category subtree, merged into one session (capped per session). |
create_deck | Generate flashcards or cloze cards; reverse also adds back-to-front cards. |
create_quiz | Generate multiple-choice questions. |
grade_card | Record a review result and update the card's FSRS schedule (called by the UI). |
due_today | Summarize what is due across all decks, and flag struggling cards (3+ lapses). |
edit_card | Change a card's front and/or back. |
refine_card | Propose splitting a card into atomic pieces, or rewriting it to test understanding. |
apply_refinement | Persist a refinement after the user approves the proposed cards. |
capture | Turn something that just burned you (a bug, a missed question) into draft cards. |
apply_capture | Persist captured cards after the user approves them. |
rename_deck | Rename a deck (also moves it in the category tree). |
delete_card | Remove a single card. |
delete_deck | Remove a whole deck. |
Card generation follows Memora's quality rules (atomic single-concept cards, 1-5 word answers, active recall, unambiguous, no answer leakage, application over definition), based on Wozniak's *20 Rules of Formulating Knowledge*. New cards are linted on write and flagged (never blocked) so Claude can revise them.
A tool declares a ui:// resource. When Claude calls the tool, the host (Claude Desktop) fetches that resource, renders its HTML in a sandboxed iframe, passes the tool result to the UI, and the UI talks back to the host over JSON-RPC (to grade cards and report progress to the model).
Open Settings > Developer > Edit Config and add Memora under mcpServers:
{
"mcpServers": { "memora": { "command": "npx", "args": ["-y", "@servation/memora-mcp", "--stdio"] } } }
Then fully quit Claude Desktop (from the system tray) and relaunch. memora appears under Settings > Developer, pre-loaded with a few sample decks.
Your decks are stored in ~/.memora/decks.json (override the path with the MEMORA_DECKS environment variable). Hand-edit that file or let Claude manage it.
Run from source instead
git clone https://github.com/Servation/memora-mcp.git
cd memora-mcp npm install npm run build
Point the config at the built entry with an absolute path (decks then live in the repo's data/decks.json):
{
"mcpServers": { "memora": { "command": "node", "args": ["C:\\path\\to\\memora-mcp\\dist\\main.js", "--stdio"] } } }
</details>
review my World Capitals deckmake me a deck of 10 Spanish travel phrasesmake a reversible deck of 10 Spanish words (drills both directions)make a fill-in-the-blank deck about the water cycle (cloze cards)quiz me with 10 multiple-choice questions on the solar systemturn what we just discussed into a deck called "Photosynthesis"study my LLM categorywhat's due today?@modelcontextprotocol/sdk plus @modelcontextprotocol/ext-apps, stdio transport (Streamable HTTP also available).vite-plugin-singlefile.ts-fsrs (FSRS).node once built (no bun or tsx needed).{
"Deck Name": [ { "front": "Capital of France?", "back": "Paris" } ] }
~/.memora/decks.json when installed (or data/decks.json from source); override with MEMORA_DECKS.create_deck, create_quiz, and grade_card write here atomically."options": ["...", "..."]; its back is the correct option.[...] in the front, with the hidden term as the back.due date and an FSRS srs block as you review them; cards without them are treated as new.memora-mcp/
├── server.ts # MCP tools + the ui:// resource ├── decks.ts # data model, decks.json storage, result builder ├── scheduling.ts # FSRS scheduling + review ordering ├── main.ts # entry: stdio (Claude Desktop) or Streamable HTTP ├── mcp-app.html # UI entry HTML (bundled by Vite) ├── src/ │ ├── mcp-app.tsx # review orchestrator (flip / quiz / cloze, grade -> model) │ ├── deck-lib.tsx # tree, mind map, card list, quiz/cloze views, helpers │ ├── mcp-app.module.css │ └── global.css # host theme variable fallbacks (light/dark) ├── data/decks.json # editable decks, read live ├── media/ # README images ├── vite.config.ts # single-file bundle config └── tsconfig*.json
npm run dev # vite watch (UI) plus tsx server on http://localhost:3001/mcp
npm run typecheck # tsc --noEmit
For fast local iteration you can also run the app against the MCP Apps reference host (basic-host) from the ext-apps repo.
See TODO.md for the backlog: npm + MCP Registry publishing, cross-client hosting (Streamable HTTP), tests around parsing and scheduling, and a real screen-capture demo GIF.
MIT