Learning Resources
fluidrecall.com
An MCP server for spaced-repetition flashcards that manages accounts and sessions, serves due cards, reveals answers, and exports snapshots.
ENDPOINT 1
https://fluidrecall.com/mcp
MCP server metadata
- Name
- fluid-recall
- Version
- 1.0.0
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 UI, startSession, nextDue, gradeAndNext, listDue, listDecks, inventoryDeck, and listDeckCards render a card automatically from their own results. No extra call is needed, and a card never shows an answer before revealCard. Every tool works the same without UI. Read GET /muse/skill.md for the full drill order.
Known tools 34
startSessionWrite when no bearer (mints a token), read when a bearer is present.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.fluid-recall]
url = "https://fluidrecall.com/mcp"
enabled = trueClaude Code
.mcp.json
{
"mcpServers": {
"fluid-recall": {
"type": "http",
"url": "https://fluidrecall.com/mcp"
}
}
}Claude Desktop
Settings → Connectors → Add custom connector
Name: fluid-recall
Remote MCP URL: https://fluidrecall.com/mcpAdd this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"fluid-recall": {
"url": "https://fluidrecall.com/mcp"
}
}
}Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"fluid-recall": {
"type": "http",
"url": "https://fluidrecall.com/mcp"
}
}
}Generic MCP
Client-specific MCP configuration
{
"name": "fluid-recall",
"transport": "streamable-http",
"url": "https://fluidrecall.com/mcp"
}MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://fluidrecall.com/api/mcp
MCP server metadata
- Name
- fluid-recall
- Version
- 1.0.0
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 UI, startSession, nextDue, gradeAndNext, listDue, listDecks, inventoryDeck, and listDeckCards render a card automatically from their own results. No extra call is needed, and a card never shows an answer before revealCard. Every tool works the same without UI. Read GET /muse/skill.md for the full drill order.
Known tools 34
startSessionWrite when no bearer (mints a token), read when a bearer is present.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.fluid-recall]
url = "https://fluidrecall.com/api/mcp"
enabled = trueClaude Code
.mcp.json
{
"mcpServers": {
"fluid-recall": {
"type": "http",
"url": "https://fluidrecall.com/api/mcp"
}
}
}Claude Desktop
Settings → Connectors → Add custom connector
Name: fluid-recall
Remote MCP URL: https://fluidrecall.com/api/mcpAdd this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"fluid-recall": {
"url": "https://fluidrecall.com/api/mcp"
}
}
}Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"fluid-recall": {
"type": "http",
"url": "https://fluidrecall.com/api/mcp"
}
}
}Generic MCP
Client-specific MCP configuration
{
"name": "fluid-recall",
"transport": "streamable-http",
"url": "https://fluidrecall.com/api/mcp"
}MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for fluidrecall.com was fetched 2026-10-01T23:44:01.290Z.
fluidrecall.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.