Fluid Recall MCP MCP server

Fluid Recall provides a deterministic system of record for spaced recall, allowing AI agents to manage decks, cards, and due times. Agents interact via MCP tools to send ratings and receive next due times, serving as the backend for agent-coached study sessions without a traditional user interface.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Fluid Recall

MCP endpoint (Streamable HTTP)

https://fluidrecall.com/mcp

Vendor documentation

What you can do with it

Manage spaced repetition decks and cards
Retrieve due items for agent-coached practice
Submit ratings to update recall schedules
Export manifest and review data via API

Tools advertised by the last live check:

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
applyDeadlinePlan
exportManifest
exportSnapshot
submitFeedback

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http fluid-recall-mcp https://fluidrecall.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add fluid-recall-mcp --url https://fluidrecall.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable fluid-recall-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "fluid-recall-mcp": {
      "url": "https://fluidrecall.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "fluid-recall-mcp": {
      "type": "streamableHttp",
      "url": "https://fluidrecall.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start fluid-recall-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "fluid-recall-mcp": {
      "type": "http",
      "url": "https://fluidrecall.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http fluid-recall-mcp https://fluidrecall.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "fluid-recall-mcp": {
      "url": "https://fluidrecall.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "fluid-recall-mcp": {
      "serverUrl": "https://fluidrecall.com/mcp"
    }
  }
}

See all 1,687

Do you run Fluid Recall MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing