Skip to main content
Glama
jerrl10

Recall

by jerrl10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Recall

No user-submitted related servers found.

    Related Servers

    • obsidian-dev-memory

      jmjava
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.
      7
      1
      MIT

    • vault-mcp

      andreymudri
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to use an Obsidian vault as long-term memory, with search, reading, and writing of notes, plus automatic capture of learnings that are propagated to MOCs, daily notes, and the knowledge index with git commits.
      9
      23 npm
      MIT

    • central-brain

      DycandX
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to access a local Obsidian vault as a unified knowledge base, with hybrid semantic search, project context retrieval, agent session logging, and reusable skill loading.
      1
      MIT

    • Obsidian MCP Server

      Vasallo94
      A
      license
      B
      quality
      D
      maintenance
      Connects AI assistants directly to Obsidian vaults with intelligent note creation using templates, semantic search, smart tagging to avoid duplicates, and specialized agent roles (Guardian, Researcher, Connection Weaver) for managing knowledge bases.
      35
      10
      MIT
    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

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    note_search and note_context both retrieve relevant notes, but their use cases are clearly separated: one is for pre-capture lookup with excerpts, the other is for session-start context gathering. note_capture, note_read, and vault_health have distinct, non-overlapping purposes.

    Naming Consistency4/5

    Four tools follow a predictable note_* prefix pattern with clear action or intent, while vault_health is a reasonable diagnostic outlier. The naming is consistent enough that an agent can infer behavior, with only minor deviation from a pure action-oriented convention.

    Tool Count5/5

    Five tools is well-scoped for a personal-knowledge recall server: search, read, capture, context, and health cover the essential workflow without bloat or redundancy. Each tool earns its place.

    Completeness5/5

    The tool set covers the full knowledge lifecycle: discover existing notes, read them, capture new material while folding duplicates, and pull relevant context into the conversation. vault_health also addresses the diagnostic dead-end when something fails, and deletion is reasonably absent for a durable-note system.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources