Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Flashcards, quizzes, and cloze cards with spaced repetition, as an inline MCP App.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-mcp"
]
}
}
}Run this in your terminal
claude mcp add memora -- npx -y @servation/memora-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"memora": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@servation/memora-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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account Servation, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
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
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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
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.
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