applyDeadlinePlan — Fluid Recall MCP Tool
applyDeadlinePlan
(apply deadline plan) 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 applyDeadlinePlan from your client
- Claude Code Fluid Recall applyDeadlinePlan run in your project directory
- Claude Desktop Fluid Recall applyDeadlinePlan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fluid Recall applyDeadlinePlan ~/.cursor/mcp.json
- VS Code Fluid Recall applyDeadlinePlan .vscode/mcp.json
- Zed Fluid Recall applyDeadlinePlan ~/.config/zed/settings.json
- Windsurf Fluid Recall applyDeadlinePlan ~/.codeium/windsurf/mcp_config.json
- Cline Fluid Recall applyDeadlinePlan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fluid Recall applyDeadlinePlan ~/.gemini/settings.json
- Grok Fluid Recall applyDeadlinePlan .mcp.json (in your project root)
- ChatGPT Fluid Recall applyDeadlinePlan Settings → Connectors → Advanced → Developer mode
- Claude.ai Fluid Recall applyDeadlinePlan Settings → Connectors → Add custom connector
- LangChain Fluid Recall applyDeadlinePlan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://fluidrecall.com/mcp
Other tools on this server
- createAccount
- bootstrapAccount
- startSession
- nextDue
- gradeAndNext
- getStudySettings
- get_profile
- updateStudySettings
- createDeck
- updateDeck
- setDeckNote
- listDecks
- archiveDeck
- unarchiveDeck
- addCard
- addCards
- updateCard
- setCardNote
- retireCard
- unretireCard
- moveCard
- listDue
- listUpcomingNew
- listDeckCards
- inventoryDeck
- getCard
- revealCard
- recordReview
- undoReview
- previewDeadlinePlan
- 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.