Skip to main content
Glama
Sign In
Recall MCP

Recall MCP

by mindnext-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Recall MCP

No user-submitted related servers found.

    Related Servers

    • HypatiaHoard

      Luissalet
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to create, search, and manage locally stored spaced-repetition flashcards, quiz users in chat with front-only prompts, and grade their answers using SM-2 scheduling.
      MIT

    • srs-mcp

      happymario123
      A
      license
      A
      quality
      D
      maintenance
      Provides spaced-repetition scheduling with the SM-2 algorithm as MCP tools, enabling agents to manage review items like flashcards or vocab locally. It supports adding, grading, and listing due items, plus optional pro features for export and forecast.
      6
      MIT

    • srs-mcp

      klutometis
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to perform spaced-repetition learning with FSRS scheduling, including adding cards, reviewing due cards, and grading recall, using a headless SQLite or Postgres backend.
      9
      34 PyPI
      2
      MIT

    • Poppy

      trags-garden
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to store decisions, preferences, and lessons in a local SQLite store, then recall the most relevant ones on demand. Runs fully local — no cloud, API keys, or per-query cost — and also exposes forget and consolidate operations.
      2
      Apache 2.0

    • memex

      jTas6281
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to save and recall atomic markdown knowledge cards with bidirectional links across sessions, so learning persists and builds over time. Cards live as plain, git-syncable files readable by both agent and human, with no vector database or embeddings required.
      9 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource and action: deck creation/listing, card add/list/delete, due-card retrieval, and review recording each have a distinct purpose. The main soft spot is list_decks vs deck_stats, which both surface counts and due-today numbers, and list_cards vs due_cards, which could be confused at a glance, though the descriptions resolve both.

    Naming Consistency4/5

    Seven of eight names follow a predictable verb_noun snake_case pattern (list_decks, create_deck, add_card, list_cards, review_card, delete_card). The two noun-only names, due_cards and deck_stats, deviate from that pattern but remain readable and unambiguous.

    Tool Count5/5

    Eight tools is well within the ideal range and every one earns its place: deck management, card management, review scheduling, and stats. Nothing feels redundant or missing at the structural level.

    Completeness3/5

    The review lifecycle is fully covered (add -> due -> review -> reschedule -> delete), but deck management is incomplete: there is no delete_deck or rename/update_deck, and cards cannot be edited after creation. An agent asked to rename a deck, remove a deck, or fix a typo in a card would hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources