mocop
Browse · Docs · Guide · Analyze

Fluid Recall

MCP server by Fluid Recall · mcp

Fluid Recall is the system of record for spaced recall. You are the coach. The personal API token is the tenant: never send a userId. listDue never returns answers: say the prompt, wait for the person to answer out loud, then revealCard for the one answer. Schedule only from recordReview's dueAt. Never invent an interval. New cards per study day are capped by each deck's newCardsPerDay; choose that integer with the person. There is no default of 20. No bearer? createAccount, bootstrapAccount, and startSession (no bearer) mint a token. Save it for Authorization: Bearer calls. A missing or wrong bearer on other tools is HTTP 401. FR_API_TOKEN is not a drill tenant. Agents may use these MCP tools, the Markdown doors at /api/v1/agent and /api/v1/dev, or JSON /api/v1. All three are first-class. listDue, listUpcomingNew, listDeckCards, inventoryDeck, getCard, revealCard, startSession, nextDue, and gradeAndNext include deckNote and cardNote (null when unset). In hosts that support MCP Apps U…

Endpoint: https://fluidrecall.com/mcp

Verification: observed. Source: crawl.

Capabilities (38)

  • 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
About · Contact · Privacy