Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Flashcards, quizzes, and cloze cards with spaced repetition, as an inline MCP App.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add memora -- npx -y @servation/memora-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"memora": {
"command": "npx",
"args": [
"-y",
"@servation/memora-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"memora": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@servation/memora-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Servation 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Georgia MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
An MCP server for Georgian public data, read from the organizations that publish it.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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