unarchiveDeck — Fluid Recall MCP Tool
unarchiveDeck
(unarchive deck) is one of 34 tools on the
Fluid Recall
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unarchiveDeck from your client
- Claude Code Fluid Recall unarchiveDeck run in your project directory
- Claude Desktop Fluid Recall unarchiveDeck ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fluid Recall unarchiveDeck ~/.cursor/mcp.json
- VS Code Fluid Recall unarchiveDeck .vscode/mcp.json
- Zed Fluid Recall unarchiveDeck ~/.config/zed/settings.json
- Windsurf Fluid Recall unarchiveDeck ~/.codeium/windsurf/mcp_config.json
- Cline Fluid Recall unarchiveDeck ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fluid Recall unarchiveDeck ~/.gemini/settings.json
- Grok Fluid Recall unarchiveDeck .mcp.json (in your project root)
- ChatGPT Fluid Recall unarchiveDeck Settings → Connectors → Advanced → Developer mode
- Claude.ai Fluid Recall unarchiveDeck Settings → Connectors → Add custom connector
- LangChain Fluid Recall unarchiveDeck pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://fluidrecall.com/mcpOther tools on this server
- createAccount
- bootstrapAccount
- startSession
- nextDue
- gradeAndNext
- getStudySettings
- get_profile
- updateStudySettings
- createDeck
- updateDeck
- setDeckNote
- listDecks
- archiveDeck
- addCard
- addCards
- updateCard
- setCardNote
- retireCard
- unretireCard
- moveCard
- listDue
- listUpcomingNew
- listDeckCards
- inventoryDeck
- getCard
- revealCard
- recordReview
- undoReview
- previewDeadlinePlan
- applyDeadlinePlan
- exportManifest
- exportSnapshot
- submitFeedback
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.